PDA

Click to See Complete Forum and Search --> : Regarding ActiveX Data Object compatibility


rameshbaboov
Dec 8th, 2000, 01:58 PM
Hi all,

I had an application written in VB that uses ADO1.5. When i installed visio 2000 in that PC, the ADO got upgraded to ADO2.1 and the application failed to start, stating illegal exception error in file MSado15.dll. I manually unregistered the files msado15.dll and msador15.dll (of version 2.1), renamed and copied the same files of version 1.5 , registered the version, and started the application and it was found to be working.Then i uninstalled the Visio.


Later, i again installed the Visio and found the application to be working. I checked the ADO version and it was 1.5 and not upgraded to ADO2.1

I am very much confused with this behaviour and i can't recompile my application to work with ADO2.1 or greater due to some other problem.

Can any one can explain the following:

Why the app failed to work with ADO 2.1?
Why the Visio did not upgrade the ADO second time?

Regards

Jan 1st, 2001, 09:29 PM
Originally posted by rameshbaboov
Hi all,

I had an application written in VB that uses ADO1.5. When i installed visio 2000 in that PC, the ADO got upgraded to ADO2.1 and the application failed to start, stating illegal exception error in file MSado15.dll. I manually unregistered the files msado15.dll and msador15.dll (of version 2.1), renamed and copied the same files of version 1.5 , registered the version, and started the application and it was found to be working.Then i uninstalled the Visio.


Later, i again installed the Visio and found the application to be working. I checked the ADO version and it was 1.5 and not upgraded to ADO2.1

I am very much confused with this behaviour and i can't recompile my application to work with ADO2.1 or greater due to some other problem.

Can any one can explain the following:

Why the app failed to work with ADO 2.1?
Why the Visio did not upgrade the ADO second time?

Regards


Since you say you manually unregistered the ADO files I would bet that in the registry the files were never actually removed and as such you will probably find them still listed and so the Visio program believes they are still available and gives you no sign of a problem. at some point you may find that the versions will be incompatible and will cause a specific use to fail. i.e. you ask for a higher function that your registered dll 1.5 has and your program is unable to process a request. mind you this is just an experienced guess, so look at your egistry and you should have your answer.