Hi,

I have a little VB6 app that uses comdlg32.ocx. The app was developed and compiled on a Windows 2000 P.C. and runs just fine on the development box and a number of other Win2000 and some WinNT boxes.

However, in attempting to run this app on a particular WinNT box, I get the following error:

Run-time Error 429: ActiveX Component Can't Create Object

I've looked at the following KB article, but I'm not sure if it applies in this case:

http://support.microsoft.com/default.aspx?scid=kb;en-us;281848

Has anyone else run into this problem with the Common Dialog control in a VB6 app? If so, what was the solution?

Note that the organization I developed the app for does not believe in using commercial install packages (I use Installshield Express 3.5 for my VB projects and have never had problems).

The way they deploy apps is to create an install package (MSI file) using Windows installer in a "P.C. configured with the Corporate image" - i.e. standard P.C. They move the exe file to this P.C. and try to get it to work with the "standard image". Once they get it working, they create the MSI file. The problem they are having now is that the program causes error 429 when running on this box. I think there are some dependency issues with comdlg32.ocx that could easily be resolved by using a commercial install package ...

Also, my experience has always been to build the set-up package on the development box (in my case using InstallShield Express) - is this a normal practice?


Thanks, Al