For a Professional: VB5, DAO 3.6

[cps]

A challenging question for someone:

We recently had to replace a development system in our office. The old system had Visual Basic 5 which was using a DAO 3.6 reference for a project. We were able to manipulate Access97 databases using the "opendatabase" command.

The new PC has Visual Basic 5, but it cannot use a DAO 3.6 reference for our project because we get a "Run time error '3633': Can't load DLL 'MSJET35.DLL'".

Extra Info:
The old system was a DAO 3.5 environment with the dao360.dll file manually copied and registered. On the old PC we were able to create, using the 3.6 reference, an exe that manipulate Access 97 databases.

The new system is a DAO 3.5 environment with the dao360.dll file manually copied and registered. On the new PC we are not able to create, using the 3.6 reference, an exe to manipulate Access 97 databases.

It is our goal to remain at the DAO 3.5 environment. We have no desire to use any DAO 3.6 DLLs (ie. msjet40.dll) except for dao360.dll.

Why are we fighting with this?:
In our experience, using a complete DAO 3.6 environment for development requires our clients to reinstall the complete application due to new DLLs and registrations as opposed to us being able to rework one exe and send it out as a stand-alone update. Our clients use our apps to get information from both Access 97 and 2000 databases. With our previous development PC we could create a single installation or exe that accomplished this task.

Conclusion:
Did we just luck out with the old development PC? Are we having a pipe dream hoping that we can reference DAO 3.6 in the manner described above?

Any help that you could offer this situation would be greatly appreciated.

Thank you,
Adam Nicholas

 

[Snaggs]

OK, I'll take a stab at it. I don't have the DAO360.DLL on my system as of now since it's being upgraded. The DAO360.DLL has some dependencies that it must have on the machine before you can access all the functionality from the DLL. Evidently one of the dependencies is the MSJET35.DLL that you mentioned earlier.

In order to determine the dependencies of the dll, locate the dll on your system and then open it with the quickview program. If you double click on the DLL, it should ask you how you want to open it. Select QuickView from the list.

Scroll down the list until you see a section called "Import Table". This is a list of DLL's that the DLL you're looking at is dependent on. Be sure that all these DLL's listed in the "Import Table" section, exist on the new system.

MSJET35.DLL if I recall correctly, is usally located in the Windows System direcotry. However, sometimes it gets installed in the C:\Program Files\Commmon Files\Microsoft Shared\DAO. If you still have access to the old machine, check for the location of the dependent files on that machine and see if you can hunt them all down. It would be wise to check the versions of the DLL's before just copying them over to the new machine. Also make a backup of any dll's that you replace on the new machine. Some of the dependent dll's may not have to be registered.

As a final thought, if you still can't get it to load on the new development machine, install the appliaction on the development machine and let the Setup program place the needed DLL's on the system and register them for you.

Good Luck! Snaggs
tribesaddict@swbell.net

 

[swilliams]

Something to check quickly that might solve the problem, but then again, might not!!

Did the old machine have Office 2000 installed, and if so does the new machine?? DAO3.6 object library is installed with Office 2000, but DAO3.5x is installed with Office 97.

Simon

 

[jimgao]

i prefer to make a new install package including dll and register by itself