The only way to guarantee that it'll work on every workstation without
problems is to make sure that every workstation has exactly the same version
of each of the referenced files in exactly the same location.
To see what's really going on, read what Michka has at
http://www.trigeminal.com/usenet/usenet026.asp
Terry Kreft and Dev Ashish wrote a References Wizard that may help you.
Check
http://www.mvps.org/access/modules/mdl0022.htm at "The Access Web".
This can be installed as an Access add-in, which you can then invoke through
the Tools | Add-Ins menu option, or you can call it from your program
(instructions are included in the download). While it doesn't store details
of what referenced files should be present, it attempts to correct broken
references by trying to reregister them using their GUIDs
Peter Walker has an interesting approach that you can download (for free)
from
http://www.papwalker.com/dllhell/index.html. Peter not only stores the
details about each reference, he stores a binary copy of the file as well!
In this way, if a broken reference is found, the file is written to the same
folder as the application, and a reference set to it. Note that this does
have the potential of impacting other applications, since it can change what
version of the file is registered in the registry.
--
Doug Steele, Microsoft Access MVP
(No private e-mails, please)
Albert said:
I have this problem also. Can we use any property or method to program
Access to use those missing library to make it consistency before
application run everytime ?
Albert