Tom Wickerath replied to Paul
02-Feb-10 02:40 PM

Hi Paul,
Sometimes it is, and sometimes it is not. My advice is to first verify that
your database does not have extra checked references that are not needed, and
that any VBA code compiles without errors.
I often times see databases that have a bunch of unnecessary references
checked. Make a backup copy of your database. Compile your VBA code first, to
ensure that you do not have any lingering compile-time errors. Then make a
note of your current checked references, and then start eliminating any
questionable references one-by-one, doing a compile after removing each one.
If your code continues to compile without an error after removing a checked
reference, then you did not need that checked reference. It is best to always
loading libraries that are not used. There is one reference that I have seen
checked--I am thinking it is called Utility.mda, but I am a bit foggy on that
memory--that is no longer supported in A2007. So, if your 2003 project
happens to include a reference to this particular library, you might
experience trouble on that one.
Tom Wickerath
Microsoft Access MVP
http://www.accessmvp.com/TWickerath/
__________________________________________