Build EXE creates a failing Executable VFP9 2

[SteveBoard]

I've been working on a simple executable (stand-alone) in VFP but the BUILD of the project creates an EXE that does not run standalone in Windows. It works in the VFP development environment.

From Windows, the EXE stalls after the startup step and fails to display the first form. Other previously compiled and built EXE programs in Fox still work fine on this computer.

Issues I've eliminated:
--READ EVENTS is included after the DO FORM
--Support files from VFP are on the system (else why would other EXEs work?)
--Recompile and rebuild project have been done
--I've put WAIT WINDOW in the startup code to be sure the first step occurs. It shows up properly in Windows, so that step is executing; the form then fails to come up.

I've tried the same project on other machines with the same result. It behaves like I've left out the read events step but I didn't. I've made dozens of VFP executables and never had this problem. This is VFP9 and SP2. Windows XP.

 

[Nigel Gomm]

Steve,

put the line

coverage=coverlog.txt

into the config.fpw file

then after running your .exe open up the coverlog.txt file in notepad and you can follow what happened.

nigel

 

[Olaf Doschke]

Good advice from Nigel.

Also, if you can see the exe in the process list of the task manager, the read events is in action.Something went wrong, can't see it from here.

Do you set _screen.visible = .f., do you have a SCREEN=OFF in a config.fpw, then your form must be top level or you won't ever see it.

If your main form initially started by the DO FORM is modal, you won't need a red event. if you DO FORM NAME xyz or LINKED to a variable, but that variable is a local variable, the form will vanish too, if the variable is released.

Bye, Olaf.

 

[SteveBoard]

Thank you both.

The screen=off was the problem. It now works.

I was able to learn the coverage log in the process, so thanks to Nigel also.