Reference Libraries??

gmatriix

Registered User.
Local time
Today, 07:10
Joined
Mar 19, 2007
Messages
365
Hello All,

I am having trouble with my Reference Libraries not being the same or missing when I am using my access db from a different machines. The code works fine one one machine but not on another.

Is there a way to keep my libraries the same and work on any machine I put it on?

Thanks,
 
I would like to add the issue of 64 bit vs 32 bit. I'm currently experiencing this with Autocad. The reference libraries are the same, however the reference added at work has to be removed and put back at home for the code to work, and vice versa.
 
I get around the lack of Intellisense for Late Binding by using what could be called (for want of a better name) "Mixed Binding" during development. The reference is included and I Dim as the specific object type as in Early Binding.

But I use the Late Binding "CreateObject" command to instantiate the object.

When completed, the reference is removed and the Dim changed to "As Object". It is easy to do a find and replace on the whole project and the CreateObject lines don't need to be touched.
 
This is great! Thanks for the advise,

Is there a way to have the code to refer to a default (complete set) library that will work on most all machines.

For instance, some where on the network there is a complete set library that all my machines refer to for libraries to ensure that they are all the same.

Idk......just asking

Thanks
 
Hello All,

If make my access db a excutable program and install it on each machine would that take care of my reference library problem?

Thanks
 
No. The references used by your application are held in your machine and do not get transferred with your program.

You can make a reference to your database but this will only make the modules you have written it available.

In the same way the modules for the references you see in the list in VBA are held in dll and exe files in Windows. Different systems have references to different version of those files. It isn't something to mess with.

As we said above your only real option to broaden compatibility is to use Late Binding. This is a generic call to the system to provide the registered version of a library rather than the specific library version called in Early Binding.
 

Users who are viewing this thread

Back
Top Bottom