Mdac WRONG Version
Hi everybody,
I'm building a package with Wise Package Studio 7, from a legacy setup. It's about a old software and it has Mdac 2.7 included, I've compiled and installed this package on a test computer. The application is working perfectly, but there is a problem with another things that have to be together on the same PC, such as vbscript using ADO. I think the problem is caused by Mdac 2.7 installation, because originally the computer has Mdac 2.8.
So, do you know how to skip or delete Mdac 2.7 installation? I've tried to install Mdac 2.8 after Mdac 2.7 installation, but I've found an error message "This setup doesn't support installing on this operating system"
I'm building a package with Wise Package Studio 7, from a legacy setup. It's about a old software and it has Mdac 2.7 included, I've compiled and installed this package on a test computer. The application is working perfectly, but there is a problem with another things that have to be together on the same PC, such as vbscript using ADO. I think the problem is caused by Mdac 2.7 installation, because originally the computer has Mdac 2.8.
So, do you know how to skip or delete Mdac 2.7 installation? I've tried to install Mdac 2.8 after Mdac 2.7 installation, but I've found an error message "This setup doesn't support installing on this operating system"
0 Comments
[ + ] Show comments
Answers (3)
Please log in to answer
Posted by:
jmaclaurin
12 years ago
It is probably a custom action. You should start by looking in the InstallExecuteSequence table.
Without looking it up, I don't think MDAC can be forced to downgrade. There are a number of good articles (wikipedia has one I think) on MDAC that will tell you what to look for in the different versions and what comes with which OS/SP.
Without looking it up, I don't think MDAC can be forced to downgrade. There are a number of good articles (wikipedia has one I think) on MDAC that will tell you what to look for in the different versions and what comes with which OS/SP.
Posted by:
anonymous_9363
12 years ago
A tactic which has worked for me with idiot installers like this is to:
- Uninstall MDAC 2.8
- Install MDAC 2.7
- Re-install MDAC 2.8
The remnants of the 2.7 install should be enough to satisfy the installer that 2.7 is (or, at least, was) installed and it will skip re-installing.
- Uninstall MDAC 2.8
- Install MDAC 2.7
- Re-install MDAC 2.8
The remnants of the 2.7 install should be enough to satisfy the installer that 2.7 is (or, at least, was) installed and it will skip re-installing.
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.