DAO causing problems?

Printable View

Jun 15th, 2009, 05:11 PM
CoachG

DAO causing problems?

I'm having some problems with an app on the computers of some of the people testing it. They're getting this error upon start up of the app

System.Runtime.InteropServices.COMException (0x80040154): Retrieving the COM class factory for component with CLSID {00000100-0000-0010-8000-00AA006D2EA4} failed due to the following error: 80040154.

There are only three COM references in my project - one of them is dao.dll - the app works fine for some people but for the two it does not at least one of them is using Vista 64 bit (the other I am still waiting to hear on his o/s but I'm guessing its 64 bit). Does DAO cause problems with 64 bit systems and if so should I just remove all the DAO and make it ADO.NET code or is there some other kind of workaround?

The app is being installed on the 64 bit machine to C:/Program Files(x86) - is there a different install path that would help the app run? Is it possible this issue has nothing to do with a DAO and Vista 64 bit link?

The error does not point directly at a line of code - only the module that contains it and in the declarations of that module is

Friend DAODBEngine_definst As New dao.DBEngine

which is why I am assuming this is dao related.

Any help would be appreciated.
Jun 15th, 2009, 05:13 PM
techgnome

Re: DAO causing problems?

Any particular reason why you're using DAO with .NET? I know it's going to require some effort, but you may have better luck (certainly in the long run) by moving to ADO.NET and re-writing (yes, from scratch) the code to remove DAO.

-tg
Jun 15th, 2009, 06:59 PM
CoachG

Re: DAO causing problems?

It was a VB6 project that I carried over to .NET

I'm assuming that I will have to learn ADO.NET but I was just wondering if there was another alternative first (or even to make sure that this is even the source of the problem)
Jun 16th, 2009, 07:30 AM
si_the_geek

Re: DAO causing problems?

DAO is almost certainly the source of the problem.

The help for VB6 (written back in 1998) explicitly said not to use it for new projects, because it was on the way out back then.

For a few years now it has been officially "obsolete" (which is much worse than "unsupported"!), including an explicit warning about it not being available for 64bit versions of Windows.