object references and handling versioning issues

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Is there a standard procedure for determining the version of installed Office
libraries and 're-referencing' them to avoid the 'MISSING' error.
e.g. When I code using Outlook 11, and deploy to a machine using Outlook 10
I get errors, (same for cmdlg32 v5.0 and v 6.0)
thank you for taking the time to answer this.
 
NJS said:
Is there a standard procedure for determining the version of installed Office
libraries and 're-referencing' them to avoid the 'MISSING' error.
e.g. When I code using Outlook 11, and deploy to a machine using Outlook 10
I get errors, (same for cmdlg32 v5.0 and v 6.0)
Click to expand...


Here's an article on the subject.
http://www.trigeminal.com/usenet/usenet026.asp?1033

OTOH, it's best to avoid the issue as much as possible.
ComDlg is notorious for creating all kinds of havoc.
Actually, I was never able to successfully distribute an app
that used the bleeping thing. Others have reported that
they were successful in getting it to work in their app,
only to have it break when a user installed some other
program that installed a different version of the thing.
This is the classic DLL HELL scenario. If you're using it
to browse for a file or folder, use these instead:
http://www.mvps.org/access/api/api0001.htm
http://www.mvps.org/access/api/api0002.htm

In many cases, especially for Automation situations (e.g.
Outlook?), you should use Late Binding instead of Early
Binding so you can connect to whatever version is on the
target machine.
 
While Marshall given you some good sites for reference problems in general,
for your specific problem (different versions of Outlook on the various
machines) you should probably look into Late Binding so that you don't need
to set a reference that will end up being MISSING.

Tony Toews has an introduction to the topic at
http://www.granite.ab.ca/access/latebinding.htm
 
Back
Top