Access XP and Access 2003 Missing References

  • Thread starter Thread starter scott
  • Start date Start date
S

scott

i'm running both versions of access at home. when i installed office 2003, i
only left access xp on my pc to be compatible with the office.

i opened an old access xp database with access xp and did some work on it.
when i tried opening the access xp file at work with access xp, I got an
error.

After inspection, I looked at my references and noticed 2 missing
references:

Microsoft Outlook 11.0 Object Library
Microsoft Word 11.0 Object Library

Access XP wouldn't allow me to "uncheck" or "unload" the libraries and
wouldn't allow me to add ver. 10.0 Word and Outlook Object Libraries because
of name conflicts.

Is there a way to delete the references to the missing 11.0 Object Libaries
other than the dialog box in VBE?
 
You should be able to uncheck the references in Access XP. If I remember
rightly, though, I think you may be unable to uncheck them while code is in
'break' mode, which it will be if you encounter an error, click Debug, and
then try to uncheck the references. Try clicking the 'Reset' button on the
VBA toolbar, and I believe you should then be able to uncheck the
references. Once you've done that, you should be able to select the V. 10
references.
 
scott said:
i'm running both versions of access at home. when i installed office 2003, i
only left access xp on my pc to be compatible with the office.

i opened an old access xp database with access xp and did some work on it.
when i tried opening the access xp file at work with access xp, I got an
error.

After inspection, I looked at my references and noticed 2 missing
references:

Microsoft Outlook 11.0 Object Library
Microsoft Word 11.0 Object Library
Click to expand...

FWIW if you use late binding then you don't need to worry about these
references.

Late binding means you can safely remove the reference and only have
an error when the app executes lines of code in question. Rather than
erroring out while starting up the app and not allowing the users in
the app at all. Or when hitting a mid, left or trim function call.

You'll want to install the reference if you are programming or
debugging and want to use the object intellisense stuff. Then once
its running smoothly remove the reference and setup the late binding
statements.

Sample code:
' Declare an object variable to hold the object
' reference. Dim as Object causes late binding.
Dim objWordDoc As Object
Set objWordDoc = CreateObject(" Word.Document")

For more information including additional text and some detailed links
see my Tips page on this topic.

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
 
Back
Top