VBA References

Hi,

To the best of my knowledge - different Office versions use different Outlook Library References.
[9.0, 10.0, 11.0, 12.0]

If I want to distribute a WB with some code that manipulates Outlooks Calendar - How do I:

1) Determine, via code, the "Office" version of a particular computer ?
2) How can I change/select the appropriate Outlook Reference via VBA ?

*** Thanks in advance,

Elm

Please Login or Register  to view this content.

You write your code using the oldest reference and then convert to late binding. This means you remove the reference to the library and change Outlook specific objects to generic Objects. Also you need to add you own outlook contants if used.

Hi,

If correctly understood your reply/command, - it displays the Office Version Number - BUT does not change the reference to the appropriate library.

If this assumption is correct - I did find something - which I will have to check - and will appreciate if you will be kind to approve that I'm on the "right track":

Please Login or Register  to view this content.

Thanks, Elm

You're on the right track.

However, as Andy suggests, you should do your development using early binding, and switch to late binding when you're done, then do a regression test. That gives you IntelliSense while you're developing.

You'll get compile errors for the Outlook constants when you switch over (because you're using Option Explicit), so you'll know what constants you need to define.

Hello ElmerS,

Add this code to your macro. It will set a reference to the user's version of Outlook and allow you to early bind the object in the VBE.

Please Login or Register  to view this content.

Thank you, Leith,

I will keep your code for "emergency" purposes - meaning, in case no other, "shorter", solution will be found.

However - :
Why didn't you refer, in the code, to "Outlook 12.0 Object Library" !?

Will be back to report.

Elm

Hello ElmerS,

The reason Outlook 12.0 is missing is because I don't have Office 2007. Little difficult to verify the code if I don't have access to it. I revamped the macro to not use Environ("Path") as this not reliable. Also, I removed the Split function since this function was introduced in Office 2000. Use this code instead...

Please Login or Register  to view this content.

Hello ElmerS,

Thanks for passing that info along. I'll add it to the macro. Points to you for that.

Leith, nice code... though I would suspect that on the file closing the reference needs to be removed else you have potential for MISSING references etc... so perhaps a little tweak such that the code can be invoked to add/remove the reference -- ie via Open/Close events ?

Please Login or Register  to view this content.

Thus the above could be invoked in both Open & BeforeClose events:

Please Login or Register  to view this content.

Welcome to the forum.

Unfortunately your post does not comply with Rule 2 of our Forum RULES. Do not post a question in the thread of another member -- start your own thread.

If you feel an existing thread is particularly relevant to your need, provide a link to the other thread in your new thread.

Old threads are often only monitored by the original participants. New threads not only open you up to all possible participants again, they typically get faster response, too.