tell developers to please fix MDAC 2.8 installer

[Guest]

Archived from groups: microsoft.public.windowsxp.general (More info?)

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.

 

[Guest]

Archived from groups: microsoft.public.windowsxp.general (More info?)

Try MSDN at microsoft.com,"contact us"...

"wyocowboy" wrote:

> 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.

 

[Rock]

Archived from groups: microsoft.public.windowsxp.general (More info?)

wyocowboy wrote:

> 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.

How to Contact the Microsoft Wish Program
http://support.microsoft.com/?kbid=114491

--
Rock
MS MVP Windows - Shell/User

 

[Guest]

Archived from groups: microsoft.public.windowsxp.general (More info?)

I too am having problems with my MDAC spacifically with a program called
versacheck error message exception in module abortl60.bpl at 00005527 error
creating object. I have used version checker 2.0 and find several different
versions of MDAC installed on my system. I have also used the 2.8 installer
which apparently (according to wyocowboy) has exacerbated the problem. Can
anyone help me troubleshoot this problem.

"wyocowboy" wrote:

> 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.

 

[Guest]

Archived from groups: microsoft.public.windowsxp.general (More info?)

I too have problem with updating MDAC... espcially installing the OLEDB32
file and family of files... quite often cannot even use regsrv32 to force the
installation of the DLL. Have to reinstall XP or uninstall reinstall office
or uninstall MDAC then reinstall

pain in the neck

"wyocowboy" wrote:

> 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.