Link to home
Start Free TrialLog in
Avatar of ernesto_acosta
ernesto_acosta

asked on

Error 432 during execution time

Secuentially this problem apper as follow:

1) I made a program and works well. I compile and create an exe file
2) I uninstall VB from the machine
3) The program not work any more, because apper an error mesagge because the file msstdfmt.dll was uninstalled.
4) I install this file from the "Run" command in the Start Menu and I type "Regsvr32 c:\windows\system\msstdfmt.dll"
5) After this I execute the program and it run and show me the main form, but when I press the run button appear the run-time error 432.

¿What I can do?. ¿It's possible compile the source code with some option to make the exe file "compatible"?

Thanks

             Ernesto
ASKER CERTIFIED SOLUTION
Avatar of Nightman
Nightman
Flag of Australia image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of TheQuestion
TheQuestion

There is a Toolin Visual Studio called  depends it will tell you what dll's and active x's your program needs. Probably you deleted a dll you needed or it lost its registrtation. msstdfmt may not be the only dll needed. Then when you have vb installed use the package and deployment  and it will package your exe with all the dlls you need and you wont need vb to run on your program. he last suggestion is to install the  vb 6 runtimes which you can get from www.allapi.net
Avatar of ernesto_acosta

ASKER

Nigthman:

   My problem is that I need run the program from several PC's with Win95/98, and, of course, I can't install VB6 in these PC's, for this reason I install VB temporarilly in one of this PC's and I develop the program and noy I must uninstall (legal reason ¿you know?) VB, but I should find the way to run the EXE file whithout need VB installed.

  I install VB 6 runtime program, but the error 432 still there.

  Thanks for you help
You need to establish what components your project references. These could be type libraries, dlls or OCX's, and they are probably not installed on the other pc.

Check your project references: Any components referenced there will need to  be deployed on the other pc.
Also, check your run-time component references (ctrl-T). The same goes for any of these that are referenced.

Cheers
Night
I think I should get the points - not that I'm biased or anything ;)