For Programmers: Free Programming Magazines  


Home > Archive > Visual Basic > April 2006 > System-Wide ADO Failure









You are viewing an archived Text-only version of the thread. To view this thread in it's original format and/or if you want to reply to this thread please [click here]

 

Author System-Wide ADO Failure
PHILLIP GALEY

2006-04-28, 3:56 am

I'm running VB6 Enterprise on Windows Me. Something strange happened to my
system, where any program that uses ADODB blows up as soon as you try to
instantiate a recordset object. All my projects in VB are affected and even
other programs on my computer also blow up with a Type Mismatch error when I
try to start them.

I tried reinstalling VB6 Enterprise; but during the installation, I got
dozens of error messages about various ADO- and OLE-related DLLs that could
not be registered.

Is there any solution to this problem before I reformat my hard disk?
Thanks.


MikeD

2006-04-29, 7:56 am


"PHILLIP GALEY" <ogmios4@verizon.net> wrote in message
news:%23RGQDSpaGHA.4564@TK2MSFTNGP03.phx.gbl...
> I'm running VB6 Enterprise on Windows Me. Something strange happened to
> my
> system, where any program that uses ADODB blows up as soon as you try to
> instantiate a recordset object. All my projects in VB are affected and
> even
> other programs on my computer also blow up with a Type Mismatch error when
> I
> try to start them.
>
> I tried reinstalling VB6 Enterprise; but during the installation, I got
> dozens of error messages about various ADO- and OLE-related DLLs that
> could
> not be registered.
>
> Is there any solution to this problem before I reformat my hard disk?


Reformatting should be a last resort.

Sounds like your MDAC installation got corrupted somehow. Try downloading
MDAC from the following web site and re-installing it. That'll most likely
fix things. If not, download the Component Checker to assist in
troubleshooting what's wrong with the MDAC installation.

http://msdn.microsoft.com/data/mdac...ds/default.aspx


BTW, this is really more of a Windows or data access problem. It doesn't
really have anything to do with VB.

--
Mike
Microsoft MVP Visual Basic

Sponsored Links







Also available: Server administration forum archive | Web Design forum archive | Software forum archive | Hardware reviews archive

Copyright 2008 codecomments.com