'msadodc.ocx could not be loaded..'

[JohnBates]

Hello -

well... after using InstallShield Express to create my setup package, I ran the setup. Now I'm having problems
that were not there before.

1 When I try to run my application, a .log file is generated that says "Class MSAdodcLib.Adodc of control datPrimaryRS was not a loaded control class"
I also get "Run-time error 430 - class does not support Automation"
The grid displays but does not connect to the data control-
no data appears.


2. When I open this project in VB 6 development mode,
get "C:\WINNT40\System32\msadodc.ocx could not be loaded -
continue loading project?"

I ran mdac_typ.exe (2.1)... still get the error
I then ran regsvr32 to re-register msadodc.ocx
Still get the above errors.

Note: I'm not saying that this is InstallShield's fault;
I may have made a mistake when I was building the setup package....

Anyone have any suggestions to fix these errors?
Using VB 6 SP3 and mdac 2.1
Thanks, John

 

[VBVines]

Service pack 4 alleviated alot of issues with deployment and package setup and I think SP 5 is out now. I am going to wait on sp 5 but ap 4 is pretty good. aspvbwannab

 

[JohnBates]

VBVines - thanks for your reply. Yes, SP4 might solve this
problem - but this app was working before I built the setup
package with InstallShield. I made no changes to the VB source, just built the setup package....

John

 

[JohnBates]

Here is an ** UPDATE **

Even though I was afraid of causing even more problems...
I went ahead and took your advice VBVines, and installed
Service Pack 5 for VB 6.

This resolved all the problems I mentioned in my original post.

Thanks for your ideas.
John