I'm having a problem with broken/missing references in a db I created. I believe this is being caused by the fact that I have some users running Win 2000 w/ Office 2000/Access97 and others running Win NT w/ Office 97/Access 97. My question is...Is it ok (i.e. safe) to copy all of the DLLs that are being referenced and paste them into a seperate folder on the shared network drive? That way I could reference them from the network drive and every user would be using the same version of the DLL. Will this cause any problems? Any help would be appreciated
References...Again
- Thread starter jbg
- Start date
RichMorrison
Registered User.
- Local time
- Today, 16:32
- Joined
- Apr 24, 2002
- Messages
- 588
You wrote
<<
My question is...Is it ok (i.e. safe) to copy all of the DLLs that are being referenced and paste them into a seperate folder on the shared network drive? That way I could reference them from the network drive and every user would be using the same version of the DLL.
>>
I don't believe that will work (about 80% sure).
When you start Access, open an MDB, open a module, and finally look at "references", this is what happens:
Access looks at the registry ON YOUR DESKTOP to find names of libraries,
Access displays the path to the library that it finds ON YOUR DESKTOP.
So it will not help to copy DLLs, TLBs, OLBs, etc to a network drive.
RichM
<<
My question is...Is it ok (i.e. safe) to copy all of the DLLs that are being referenced and paste them into a seperate folder on the shared network drive? That way I could reference them from the network drive and every user would be using the same version of the DLL.
>>
I don't believe that will work (about 80% sure).
When you start Access, open an MDB, open a module, and finally look at "references", this is what happens:
Access looks at the registry ON YOUR DESKTOP to find names of libraries,
Access displays the path to the library that it finds ON YOUR DESKTOP.
So it will not help to copy DLLs, TLBs, OLBs, etc to a network drive.
RichM
