Packaging help

[capone67]

Hi Gang

This week I was given a new system at work. I have installed most of the software that was on my old system. The new system has VB6 with Service Pak 5 on it where as the old system had service pack 4 I believe. I have also installed mdac 2.6 and some other components that were needed for my specific application.

Now here is the problem. When I make the OCX and package up my activeX control on my new system using almost the exact same code as before, it works fine locally but will not work on other systems. If I go to my old system and make the ocx and package up the control that is residing on my new system the package installs properly on other systems. Now here is the big catch. If I package the ocx built on my old system using my new system the package installs correctly on other systems as well. We can use this as a temporary workaround but this is definately not a long term solution since the hard drive on the old system is scheduled to be reformatted.

Does anyone have any ideas as to where I should start looking for a solution?

Ken

 

[JohnYingling]

Sounds like a version/registration problem. If you are using Package and Deployment WIzard, check out the setup.lst file. Remember, the PDW copies some files from the REDIST directory, not your WINDOWS/SYSTEM etc. Go to MSDN.MICROSOFT.COM and do a search on the modules in your setup.lst. Some groups of files must be kept in sync.
Sorry I can't be more help. I think you've entered the dreaded DLL Hell.

 

[capone67]

Hi John

Thanks for the input. Since these are activeX controls there is no setup.lst file created.

Ken