setting references

[Guest]

Access 2003

If I set references in one Access .mdb file - will those references be
set/available to other .mde files run on the same PC? Would I have to set
them again for other database files used on the same PC?

 

[Lynn Trapp]

If those are standard libraries, then they should be. However, if they are
special libraries that you created on your machine then you will need to
make them available to all other machines.

 

[Guest]

Thanks Lynn,

Further question....once special references are established on a particular
PC - will those special references be available to ALL DATABASES (.mdb and
..mde) which are opened on that PC? In other words, are libraries referenced

 

[Douglas J. Steele]

References are on an individual MDB/MDE basis.

 

[Guest]

Thank You Doug -

I now understand that references are on an individual mdb/mde basis...but do
those references go with the mdb/mde when the db is run on a different PC?
It appears to me that I need to reset references on all PCs that my .mde is
run on - which means I have to have the .mdb to do so and I don't like
putting .mdb's on client PCs even for a short while. Please elaborate on how
references/libraries are "tagged" to a particular db. Many Thanks for your
continued assistance.

 

[Douglas J. Steele]

Each database has a References collection as part of it. The information
stored with each reference is a GUID that can be used to find the file
location in the Registry, as well as a full path to where the file is
located. That, unfortunately, seems to be what causes problems: if the
registered GUID points to a different file location on Machine B than where
Machine A had it when the database was created, Access becomes confused.

As Lynn was trying to tell you, though, if you're using the standard Access
references, then as long as you're all on the same service packs, you
shouldn't have any problems. If you're using other references, then you
should try and ensure that they're in standard locations.

Take a look at what I have at
http://members.rogers.com/douglas.j.steele/AccessReferenceErrors.html