Reference Problems 1

[Quehay]

I've got a db that works fine on my PC (using the Users version of network Frontend and Backend). When I try it on a user's PC it won't bring records in from a lookup combo box (the FindFirst / set me.bookmark = rs.bookmark Wizard-generated thing). When I step through on the User's PC I get compile errors: Can't find "String$" and "Str" functions. The bloody thing compiles just fine on my PC and I've got references to the VBA, DAO, and ADO libraries.

Also: I can't remove a reference to Forms 2.0 library although I no longer have any of those controls in use on forms.

This is pissing me off to the nth degree--the Users have Access 2000 with a full installation. What is causing this $%&*%$# problem?

Thanks in advance if you can restore my sanity

 

[Quehay]

Solution:

Import all objects into new db and set References.


Resolution:

Never ever import even tables that were created by someone else in a previous version.

 

[Francescina]

Apparently the library files on the client's computer are in another location/have been renamed/have another version.

If you want to find out which libraries can not be found then you need to open the references menu on the client's computer and search for the "(Missing)" menu message.

There is also the possibility to re-link the references by code. I think that there is an article in the ACCESS ONLINE ENCYCLOPEDIA (

http://www.unsoftwareag.com).

 

[Quehay]

Thanks for the response. By importing the objects into a fresh db instance the problem was solved. By virtue of importing tables from a db which was originally created in 97 I believe the references were skewed. This appears fairly often--people wonder why the simplest of VBA functions, e.g., Now() & Date() fail to work. The user references were intact--I debugged on user PC, but also found that the Wizard-generated code for a lookup & find combo wouldn't compile there. You get a lot of ready-made functionality with Access but occasionally there's a price for not having to "look under the hood."

 

[JoyInOK]

Interesting. I am having similar problems with a db created in 2.0 and converted to Access 2000; Date() and Error$ work fine on my maching and fail on user's machines, although the references are there (vb6e.dll). While I dread copying each of the objects in our huge db and recreating the relationships, it would probably take less time than the hours I spent today checking the version one every .dll and .exe. I'll give it a try.