MDAC 2.8 problem

[moolie]

I've gone and installed mdac 2.8 and now I am having environment and deployment issues for my app. I need to remove it from the development machine for the programmer. There is nothing on Microsoft website on how to accomplish this. Any suggestions?

 

[moolie]

Okay here's the story.

Developer X decides since we are rolling out SQL server 2000 for internal use he is going to "upgrade" his MDAC from 2.6 to 2.8. Now he is having all sorts of deployment and installation issues with the application he is developing. I need to remove 2.8 and roll back to 2.6 without rebuilding the whole machine. There are lots of registry entries affected by the install and it's threaded itself into all sorts of places. HELP!

 

[RiverGuy]

Are you sure he is not having issues simply because he is deploying installs packaged with MDAC 2.6 instead of 2.8?

 

[moolie]

Yes

The application uses activeX lib's that are registered as version 2.8 on his machine. When we install on the new machine the references are not found and show up as *missing*. We then have to manually go in and reset the reference version to the version on the client machine.

 

[RiverGuy]

Show up as missing? What development environment are you using? Are you using Access as the front end or something?

 

[moolie]

ME? ACCESS? Never...

The developer on the other hand...

Yes the application is Access 2000 front end compiled and running on the Access 2000 runtime engine connecting via ODBC to SQL Server 2000 hosted back-end on a 2003 standard edition server box.

 

[RiverGuy]

I would just try and get the developer to reference the correct version. Have him open up a VBA code window in his app, and go to Tools-->References. If the wrong version is referenced, have him uncheck it, and reference the version that the users have installed.

 

[moolie]

Tried that. When he selects the correct reference version numbers from the list everything works. He saves and compiles the app but when we go back in the version numbers have changed back to 2.8.

 

[MichelleVGates]

I don't think you can deinstall it.

MDAC is considered part of the OS, so it's a one way operation. The only thing that saved me when MDAC 2.8 didn't install correctly, but would reinstall either, was "System Restore".

MVG

 

[waynefeltham]

Hi all

I had an inssue with MDAC 2.8 not supporting something that 2.7 did (can't remember what it was now, something to do with adding parameters when using the command object I think)...anyways...

I simply got a version of 2.7 and installed that over the top and everything was fine?

I don't remember uninstalling 2.8 first? I just ran the 2.7 install.

As for the project referencing 2.8 still, I'm not sure about VBA stuff but I know that in Visual Studio, there is a reference to the ADO dll when you use the package and deploy wizard which doesn't always match up to what you have on your system (don't ask me, it'w weired!)

take a look at msado15.dll here:
C:\Program Files\Common Files\System\ado
Try running the 2.7 MDAC install again and then check to see that this file has been updated, if not, manually copy it off of another machine and then re-compile your VBA stuff.

Not sure if any of this will work...but it might

Let us know.

Cheers


Wayne

 

[moolie]

MDAC 2.6 or better includes a rollback function to rollback to the previous version installed on the same machine.

dasetup.exe /u

We tested this yesterday and it does remove the last installed version and revert to the previous version.

Therefore, if you installed 2.6, then 2.8 and then 2.7 because 2.8 didn't do what you expected; then you run the rollback you will be left with 2.6 on your machine.(2.6 is numerically the last installed version by version number.) Then you can reinstall the version you want to work with. Caution. If your last installed version was 2.6 and then you rollback to 2.5 you will loose ODBC, JET etc and will have to reinstall those drivers etc manually.