Auto update reference

[cbende2]

Hello all,



I've come to a problem where I need the reference "Microsoft Outlook xx.0 Object Library" checked.
Unfortunately not everyone in my office who is using this database uses the same version of outlook. I'm looking for some code that scans the references and checks the correct "Microsoft Outlook Object Library" upon opening the database. I've found some code but I'm very inexperienced with code in general, so any modification would greatly help!

Link to code that I found relating to this: http://www.excelthoughts.com/2005/06...nd-adding.html

[pbaldy]

I would probably use late binding, which doesn't require a reference:

http://support.microsoft.com/KB/201096

[cbende2]

I've looked into that, but more than half of the employees here will be using these specific lines of code that require the outlook library checked

[cbende2]

From my understanding, it's only good to use late binding if the lines of code are not executed that often?

[pbaldy]

What lines "require" it to be checked? Constants can't be used, but they can be replaced by their numeric values. I wouldn't say it was only good to use late binding in that instance. It is true that early binding runs faster than late binding, but I doubt you'd notice the difference.

[cbende2]

Dim olApp As Outlook.Application
Dim olExp As Outlook.Explorer
Dim olSel As Outlook.Selection

[pbaldy]

I would call those declarations rather than lines of code, but it's true they require the reference. The late binding equivalent looks like this (I've never needed Explorer or Selection, but I assume they would be similar):

Dim MyOutlook               As Object
Dim MyMail                  As Object
Dim MyAttachments           As Variant

Set MyOutlook = CreateObject("Outlook.Application")
Set MyMail = MyOutlook.CreateItem(0)  
Set MyAttachments = MyMail.Attachments

[cbende2]

Ok thank you pbaldy, I will use this if needed. As of now, I was able to browse for the older outlook version library on my computer and use it. No one has had a problem with the older version... yet

Thanks for the help though! Pretty soon, all employees will be moving to office 365, so this reference issue will only be for a short time.

[pbaldy]

No problem, good luck!