Late Binding for Outlook

[dflak]

I am trying to get the following code to be independent of whether I use Outlook 2013 or Outlook 2016. I do not want to Reference the library.

I thought

Please Login or Register  to view this content.

was all that I needed.

However the code fails on the indicated line with the error Sub of Function not defined.

Please Login or Register  to view this content.

Otherwise this code works just fine!

[rorya]

You need an Outlook.Application object to call GetNameSpace.

[dflak]

OK here is the new code. It still fails in the same spot.

Please Login or Register  to view this content.

[rorya]

You need to amend the next line to:

Please Login or Register  to view this content.

[dflak]

Well I got it working on the Outlook 2016 system. When I "port" it to my Outlook 2013 system I get: Error Message Run-Time error 429, "Active X component cannot create object." on

Please Login or Register  to view this content.

I included various Microsoft ActiveX references but none of them fix the issue.

The long list is what I tried on the 2013 system. The short list is what works on the 2016 system.

[dflak]

The Outlook 2016 is a 32-bit implementation running on a 64-bit machine. The Outlook 2013 is a 32-bit implementation running on a 32-bit machine. If that makes any difference.

[rorya]

Bitness shouldn't have anything to do with it, and you don't need any references set for this (certainly not any ADO ones that you show there). Here's a troubleshooting article for that error, which is an unfortunately common one: https://support.microsoft.com/en-gb/...e-applications

[dflak]

I was just there. Everything seems to be OK. Maybe I'll have my IT department do a reinstall on office.

[dflak]

BTW: This is the same system that ran the code with no problem with early binding.

[rorya]

Also, just FYI, you aren't actually using the constant you declared (twice).

And your SendMail code needs to create (or be passed) an outlook.application object too.

[dflak]

My original question about late binding has been answered, so I will mark this thread as solved.

I did an off-line repair of office and that did not solve the problem. I might get my IT department to do a clean re-install.

To get on with my deadline, I'm going back to the early binding on the machine that will run the code. I can set up a parallel system (different Key words -different folder) to continue testing with late binding and getting it to work on the laptop.