DAO 3.5 Object Library not compatible with VB 5.0 on Windows XP machin

[sbtechforums]

Using Microsoft DAO 3.5 Object Library reference in Visual Basic 5.0 on Windows XP machine is not working. The machine has MS-Office 97 SR2, Visual Studio 5 SP3, and DAO 3.5, DAO 3.6 alongside with JET 3.51 and JET 4.0 with MDAC version 2.7.
When trying to run the VB project, an error message "Run-time error 429: Object cannot be created" is being generated in the code where a database object is being created to point to an MS-Access 97 database. Both dlls - dao350.dll for DAO 3.5 Object Library and dao360.dll for DAO 3.6 Object Library are registered.
The project has been developed using DAO 3.5 Object Library on a Windows 2000 machine having MS-Office 97 SR2, Visual Studio 5 SP3, DAO 3.5, JET 3.51 and MDAC 2.5.
The XP machine has both DAO 3.5 and DAO 3.6, and MDAC 2.7 whereas the Windows 2000 machine has only DAO 3.5 and MDAC 2.5. Would this in anyway be causing the problem for the VB project to run on the XP machine using DAO 3.5? It works fine if we change the VB reference to DAO 3.6 instead of 3.5. But we do not want to do that, because, then the compiled project will have a different set of dlls on the client machines.

 

[Darrylles]

Hi,

I've had the same kind of problem, except across Office 97 to Office 2k with an Access application (where I used VBA).

I need 'app97' and 'app2k' Access front-ends pointing to a 'app' central database.

Both dlls are NOT registered by the way, only one of them is - I'm not sure whether it is the first or last in the list - I think it's the first (there is an order button in there) - but only one will be registered and used.

You have no option but to have multiple versions of the application, or downgrade/upgrade Office installs.

Regards,

Darrylle



"Never argue with an idiot, he'll bring you down to his level - then beat you with experience." darrylles@totalise.co.uk

 

[sbtechforums]

Thanks Darrylle. But, is there a way I can unregister DAO 3.6 manually and register DAO 3.51 and henceforth force the VB application to use DAO 3.51.