G
Guest
Not sure where to post this - please pass it on to the MS MDAC developers...
According to what I read in the various forums, this is a well-known problem
- the MDAC 2.8 installer does not correctly replace older versions of the
files. The results are not pretty, and in the words of the author of the
msdn kb article, "difficult to fix." It does trigger the alarm bells when
there exists a MS tool to check the MDAC file versions for incompatibilities.
It is then up to you to manually replace the older files with the newer
versions, if you can figure out which cab file they are in and extract them.
What a PITA.
I ended up browsing to \program files\common\microsoft shared\dasetup\ and
running dasetup /u to roll it back to the previous version. Even though the
tool identified a few mismatches, the problem was fixed.
I used to test software for a living, so I am used to green code, but not in
released product. This should not have made it out the door.
According to what I read in the various forums, this is a well-known problem
- the MDAC 2.8 installer does not correctly replace older versions of the
files. The results are not pretty, and in the words of the author of the
msdn kb article, "difficult to fix." It does trigger the alarm bells when
there exists a MS tool to check the MDAC file versions for incompatibilities.
It is then up to you to manually replace the older files with the newer
versions, if you can figure out which cab file they are in and extract them.
What a PITA.
I ended up browsing to \program files\common\microsoft shared\dasetup\ and
running dasetup /u to roll it back to the previous version. Even though the
tool identified a few mismatches, the problem was fixed.
I used to test software for a living, so I am used to green code, but not in
released product. This should not have made it out the door.