Making Sure All Desktops have the same References

[mpm32]

Hi, I created a DB that will be accessed from a network drive. I created the DB on my desktop and some of the functionallity on the DB will not work when I move the DB to the network. I am assuming this is because of the references I have chosen when I created it.

How can I add the references to the network drive? Or is it to each individual desktop pc?

I tried the code from here thread705-903662 and called the functions from a button but the DB did not work properly when I tried it on another desktop.

In the code it has the files listed. I tried to add the correct paths from what comes up in the immediate window when I run the FixUpRefs Function to the area where the paths are listed in the AddRefs Function. That didn't work either.

This is what comes up when I run the FixUpRefs function on the network DB;

----------------- References found -----------------------
reference count = 8
reference = C:\Program Files\Common Files\System\ado\msador15.dll
reference = C:\Program Files\Common Files\System\ado\msado26.tlb
reference = C:\Program Files\Common Files\Microsoft Shared\OFFICE11\MSO.DLL
reference = C:\Program Files\Common Files\Microsoft Shared\VBA\VBA6\VBE6EXT.OLB
reference = C:\WINNT\system32\stdole2.tlb
reference = C:\Program Files\Common Files\Microsoft Shared\DAO\DAO360.DLL
reference = C:\Program Files\Microsoft Office\Office\MSACC9.OLB
reference = C:\Program Files\Common Files\Microsoft Shared\VBA\VBA6\VBE6.DLL

Are these the paths that I need to enter into the AddRefs function?

Can anyone help? Once I get this sorted I am finished with this project.

 

[CautionMP]

mpm32,
Yes.

One thing to keep in mind is that the reference file needs to exist AND be registered on the host computer.

I ran into this a while ago and had to write a routine that checked the host computer for a particular file. If it didn't exist I had to copy it to the local host from the server. Then I had to register the file before the database could use it.

Do you what file is causing the issue?

CMP

[small]For the best results do what I'm thinking, not what I'm saying.[/small]
(GMT-07:00) Mountain Time (US & Canada)

 

[JerryKlmns]

I think that

reference = C:\Program Files\Common Files\Microsoft Shared\OFFICE11\MSO.DLL

referers to Office 2003

and

reference = C:\Program Files\Microsoft Office\Office\MSACC9.OLB

referers to MS Access 2000

along with

reference = C:\Program Files\Common Files\System\ado\msado26.tlb

Are there
reference = C:\Program Files\Microsoft Office\Office\MSACC.OLB
reference = C:\Program Files\Common Files\System\ado\msado28.tlb

available to select them?
And do you really need these references?

reference = C:\Program Files\Common Files\System\ado\msador15.dll

reference = C:\Program Files\Common Files\Microsoft Shared\DAO\DAO360.DLL

 

[mpm32]

Hmmm. I'm so confused. The DB works when I access it from our shared drive on my PC. But when I go to anyone else's PC, one part of the DB does not work, specifically a password routine that I wrote (really found some code and adjuted it to my use) so that users could get to an update portion of the DB if their user name and password are in the password table.

I guess I do not understand where the references need to be. When I create a DB, are the references stored on my PC or with the DB? I am assuming that they get stored on my PC since in my situation above, I can't get full functionallity of the DB from the server on others PCs.

I'm not really good at this yet, I can't write code but if I find some that might work, I can usually use that and modify it to work.

 

[JerryKlmns]

Does it compile ok from the other pcs?
Any reference MISSING when you check it from the other pcs?

 

[mpm32]

Yes, I do believe that the references were missing from the server that I put the DB on. I think I did fix it. I created a file with all of the reference .dll, .olb and .tlb files that I copied from my PC. I then put that file on the server and picked the references making sure that they pointed to the server file I created, not my drive. It seems to work ok.

Was this a viable solution? It seems to work, I just don't want it to cause problems in the future.