VBA References Missing

[aldeb]

I have a database with a form. The form has quite a bit of code. This database is on a network. On some of the computers the Form will not open. When I go into Microsoft Visual Basic Tools References I am finding the following.

MISSING: Microsoft CDO 1.21 Library
MISSING: Microsfot ActiveX Data Objects 2.1 Library

Can anyone give me some advice on this issue?

Thanks for your help.

 

[MStef]

Hello aldeb!
Disconect all MISSING references and try again.

 

[dapiaoen]

Missing references

Sorry MStef, but that was only marginally helpfull. Disconnect references? How is this done? I, too, have an large mdb application and when I hand it off to a co-worker to test, it immediately crashes because it won't compile and several references are missing. De-selecting these and re-selecting them (because they are there!) works. But, how do I make sure they don't show up as missing everytime he downloads a new version of the MDB? How can I deliver it to users if the references that are really there aren't found when they download the application?

Chris

 

[MStef]

Hello Chris!
Open any VBA (form or module), click on "Tools" (menu bar), click on REFERENCES, in "Available References"
deselect all MISSING references, and OK.
(MStef alias Štef)

 

[dapiaoen]

Missing references

Ok, I understand what you mean by deselect the missing references -- and of course have done this time after time. We are developing, so a new version gets grabbed by my coworker every day and then he has to open it and it won't run because it won't compile because of missing references.

This is unsatisfactory for two reasons.
- First, it shouldn't happen.
- Next, our mode of operation is to keep a master copy on the developer's desk, and users click a VB shell to copy to their desktop and open the MDB. This works because we are using Oracle tables so multiple copies of the MDB all access the same Oracle tables. And, it overcomes MS Access problems with sharing a single MDB. But, I'd hate to think the users will have to deselect and reselect missing reference every time.

I'm thinking there must be a way to avoid ever having Missing References, and await someone to tell me how, since it isn't in any documentation i can find..and it has to be Microsofts fault.

Chris

 

[MarkK]

In one of the databases that is working, highlight the reference that is missing in the "broken" databases. At the bottom of the reference dialog is a path to the file that provides the referenced objects.
Two possibilities are that the file being referenced...
1) does not exist on the 'broken' machines. In this case try to copy or install this file onto the machines where said file is missing.
2) is not where Access expects it to be. Run a windows search for the filename on a 'broken' machine, and if found, click the Browse button in the references dialog and set the reference manually.
Hoping this helps,

 

[jrjr]

It sounds like the references are being set on a newer release of access which will make the older versions of access appear 'broken' when they try to use it. Set the references with the oldest version of access that your users will be using and then deploy as an .mde.

 

[dapiaoen]

lagbolt and jrjr:

Thanks, making sure the references are in the right location is worth trying.
The version of Access is the same, but I am running SP3 and the co-worker is on SP2. However, the problem occurred before I updated to SP3.

In fact, the coworker will get DAO 3.6 missing, have to deselect it, close the reference widget, reopen references, then reselect DAO 3.6. In other words, it is apparent that DAO 3.6 is there and can be found, but perhaps, like you say, the files are in different locations on the two machines. The same occurs for ADO RecordSet 2.7.

I'll check the locations.

Chris