MDAC Wiped Out by Auto Update

Windows ME comes with MDAC 2.5. My MDAC got mysteriously wiped out, and
with Windows ME you can't remove it and reinstall it. You have to reinstall
Windows.

So I did that. I have a fresh installation of Windows on a clean hard disk.
Now, after a few days, I believe I discovered how the MDAC had gotten wiped
out. The Windows auto-update did its thing and the next thing you know, I'm
the proud owner of MDAC 2.7 SP1, wihch is only for Windows XP. That would
be pretty good if it worked. Unfortunately, it looks like I have to
reformat my hard disk again, in order to get any programs that use MDAC to
work, including Visual Basic recordsets and a couple of programs that I have
installed and that now give an error when I try to start them. The error
says "Run time error 13 - Type Mismatch".

I'm pretty close to certain that it was the Windows Auto-Update that did it.
I uninstalled the two windows updates that were available to uninstall, but
of course that's not going to undo the damage to the system's MDAC.

Is anyone familian with this MDAC wipe-out problem with Windows Me? There's
probably a 1 in 1,000 chance that it was caused by something other than the
Windows Auto-Update, but I believe that's what did it. Now when I run a
program source code in Visual Basic and tries to instantiate an adodb
recordset, it says Server Component Can't Create Object. I use ComCheck to
see what's happening with MDAC and it shows that my MDAC is now 2.7 SP1(XP).

Don't change anything!!!!! The MVP's are in England but should be on
here soon and there was a huge thread about MDAC that I should have paid
more attention to......but they will sort you out.

Cheers...Heather (Canada)

"Phil G" wrote in message
...
Windows ME comes with MDAC 2.5. My MDAC got mysteriously wiped out,
and
with Windows ME you can't remove it and reinstall it. You have to
reinstall
Windows.

So I did that. I have a fresh installation of Windows on a clean hard
disk.
Now, after a few days, I believe I discovered how the MDAC had gotten
wiped
out. The Windows auto-update did its thing and the next thing you
know, I'm
the proud owner of MDAC 2.7 SP1, wihch is only for Windows XP. That
would
be pretty good if it worked. Unfortunately, it looks like I have to
reformat my hard disk again, in order to get any programs that use
MDAC to
work, including Visual Basic recordsets and a couple of programs that
I have
installed and that now give an error when I try to start them. The
error
says "Run time error 13 - Type Mismatch".

I'm pretty close to certain that it was the Windows Auto-Update that
did it.
I uninstalled the two windows updates that were available to
uninstall, but
of course that's not going to undo the damage to the system's MDAC.

Is anyone familian with this MDAC wipe-out problem with Windows Me?
There's
probably a 1 in 1,000 chance that it was caused by something other
than the
Windows Auto-Update, but I believe that's what did it. Now when I run
a
program source code in Visual Basic and tries to instantiate an adodb
recordset, it says Server Component Can't Create Object. I use
ComCheck to
see what's happening with MDAC and it shows that my MDAC is now 2.7
SP1(XP).

MDAC up to the most recent MDAC2.8 SP1 are all installable on Win Me. I
would advise no-one to run the almost ancient MDAC 2.5 that formed part of
Win Me when it was first released almost six years ago.

Automatic Update will not have "wiped out" MDAC although there is a bug in
the latest KB911562 hotifx for those running MDAC 2.8 which does cause
major problems. The solution, rather than reinstalling Win Me is to
install the latest MDAC 2.8 SP1 from the Microsoft Download Centre
(http://download.microsoft.com/downlo...f/MDAC_TYP.EXE)
and then install the unbroken KB911562 hotfix for that version via either
Automatic Update or from the Windows Update site.
--
Mike Maltby
MS-MVP Windows [2001-2006]




Phil G wrote:

Windows ME comes with MDAC 2.5. My MDAC got mysteriously wiped out,
and with Windows ME you can't remove it and reinstall it. You have
to reinstall Windows.

So I did that. I have a fresh installation of Windows on a clean
hard disk. Now, after a few days, I believe I discovered how the MDAC
had gotten wiped out. The Windows auto-update did its thing and the
next thing you know, I'm the proud owner of MDAC 2.7 SP1, wihch is
only for Windows XP. That would be pretty good if it worked.
Unfortunately, it looks like I have to reformat my hard disk again,
in order to get any programs that use MDAC to work, including Visual
Basic recordsets and a couple of programs that I have installed and
that now give an error when I try to start them. The error says "Run
time error 13 - Type Mismatch".

I'm pretty close to certain that it was the Windows Auto-Update that
did it. I uninstalled the two windows updates that were available to
uninstall, but of course that's not going to undo the damage to the
system's MDAC.

Is anyone familian with this MDAC wipe-out problem with Windows Me?
There's probably a 1 in 1,000 chance that it was caused by something
other than the Windows Auto-Update, but I believe that's what did it.
Now when I run a program source code in Visual Basic and tries to
instantiate an adodb recordset, it says Server Component Can't Create
Object. I use ComCheck to see what's happening with MDAC and it
shows that my MDAC is now 2.7 SP1(XP).