Compile Errors and Library References

S

swedbera

Why would only some users receive these error messages when they open the
database, while other users are able to open it without errors? I know that
when my machine was imaged a couple of months ago, certain files were missing
and I was unable to open the Help for DAO and ADO in the Visual Basic Editor
until I had those files installed. Is it possible that they do not have the
referenced files on their machines and that is why they are getting these
error messages?

Arlene
 
D

Douglas J. Steele

swedbera said:
Why would only some users receive these error messages when they open the
database, while other users are able to open it without errors? I know
that
when my machine was imaged a couple of months ago, certain files were
missing
and I was unable to open the Help for DAO and ADO in the Visual Basic
Editor
until I had those files installed. Is it possible that they do not have
the
referenced files on their machines and that is why they are getting these
error messages?

Yes, that's quite likely: References problems can be caused by differences
in either the location or file version of certain files between the machine
where the application was developed, and where it's being run (or the file
missing completely from the target machine).

On the machine(s) where it's not working, open any code module (or open the
Debug Window, using Ctrl-G, provided you haven't selected the "keep debug
window on top" option). Select Tools | References from the menu bar. Examine
all of the selected references.

If any of the selected references have "MISSING:" in front of them, unselect
them, and back out of the dialog. If you really need the reference(s) you
just unselected (you can tell by doing a Compile All Modules), go back in
and reselect them.

If none have "MISSING:", select an additional reference at random, back out
of the dialog, then go back in and unselect the reference you just added. If
that doesn't solve the problem, try to unselect as many of the selected
references as you can (Access may not let you unselect them all), back out
of the dialog, then go back in and reselect the references you just
unselected. (NOTE: write down what the references are before you delete
them, because they'll be in a different order when you go back in)

For far more than you could ever want to know about this problem, check out
http://www.accessmvp.com/djsteele/AccessReferenceErrors.html, or check my
December, 2003 "Access Answers" column in Pinnacle Publication's "Smart
Access" (you can download the column, and sample database, for free at
http://www.accessmvp.com/DJSteele/SmartAccess.html)
 
S

swedbera

Thanks Doug.

I'll try what you mentioned and will take a look at the link you provided.

Arlene
 
Top