What is the deal with VB references? (Access 2002)

Topic

New Reply

Shouldn’t VB references register automatically? It seems that they aren’t In nwer versions of a database (a few weeks). there are references showing in older versions that are not showing in new versions. Theses are being run under the same software on the same computer. Some of the references are not even on the list in the newer version, but do show up in the older version. Anyone know what is going on with this?

Reply | Quote

Replies

Perhaps if you get specific instead of just referring to “references” in general, someone will be able to give you an answer. If you’re talking about DAO references, they don’t turn up as selected in Access 2002 databases unless you set them. ADO is the default, period, unless you are converting from an earlier version that has the DAO reference set.

Reply | Quote

The references I am referring to are the ones under the tools menu in the VB window for an access form module. There is a long list of references that I assume are found by Access when opening. Some are already checked off (ie, referenced). But the list is inconsitent between different copies of the same front end – some references are missing and some are already checked on one version but not another. It seems to be a problems with Access finding the right references for it’s needs.

Reply | Quote

The list itself is largely irrelevant and comes mostly from the registry. The only significant items are the ones checked or any that show MISSING ahead of the name. Everything else varies by version of Access, other installed applications, and what profile everything was installed in. Access doesn’t need 99% of the references it finds and can’t use the bulk of them anyhow. If some of them show “MISSING”, rather than just being missing from the list, you have a reference problem in that particular database. Usually that means that the library file is not in the location where Access expected to find it. Windows *usually* finds references if they are in the same folder as the application, but even that can break if you install a runtime version of the app in a different location than it was originally on the development machine. Some default file locations have changed between versions of Access too, so that adds to the complexity.

If you specify the particular references that are of concern to you, someone may be able to help.

Reply | Quote

This appears to be related to post 253383, which is more specific, so I’m going to lock this thread and ask that any other responses be posted to the linked thread.

Reply | Quote