Interfacing with multiple versions of Outlook 1

[KornGeek]

I have some code which sends an email via Outlook. It works fine on my computer (running Outlook 2003), but it does require a reference to the Outlook library (Microsoft Outlook 11.0 Object Library on my computer).

Some of the other computers in the office are running older versions of Outlook (2002 or 2000), and there is no immediate plan to upgrade them. If I attempt to run the database on one of these computers, the code for the database fails in all sorts of places due to the missing reference.

Since my computer does not have libraries for the older versions of Outlook, and the other computers don't have the library for Outlook 2003, how can I resolve this situation?

I was considering getting a copy of the Outlook 2000 library (the oldest I will encounter) and using this on all machines, but I am unsure how to go about ensuring that each computer has this installed. I'm also not sure about any licensing issues associated with this.

Any thoughts or suggestions on how to handle this?

 

[psemianonymous]

Research "late binding" on comp.databases.ms-access, where they do that sort of thing more often than anyone here does. The quick summary of late binding is that instead of using the Outlook.11 library, you do a

dim var as Object
var = CreateObject("Outlook.Application")

...and it goes and finds whatever version of Outlook you have and attempts to load that.

I did this same thing with Word and mailmerge, if you want to look at my FAQ. But it's probably better if you just search CDMA.

--
Find common answers using Google Groups:

http://groups.google.com/groups?group=comp.databases.ms-access

Corrupt MDBs FAQ

http://www.granite.ab.ca/access/corruptmdbs.htm

 

[KornGeek]

I looks like this is exactly what I needed. Thank you very much.