Are you deploying using InstallShield. It almost seems like a project that is running without a "READ EVENTS" under a VFP IDE. In the forms "QueryUnload" a "CLEAR EVENTS", or a pointer to routine (that does the same) will execute "house keeping" code that typically follows the READ EVENT instruction.

I have a similar issue - and I think I did all my house keeping. When I run my EXE from inside VFP, I get an access denied when I try to erase the exe (so I can test from the "source" set) from the command window.

I recently moved some OCX to a "distribution" license implementation (VCX for oleclass reference). Before I did that, my VFP would just lock up and want to send M$ an error report. Now I get the "access denied" message and have to exit VFP to erase. The exe does not show up in Task Manager. Is your exe in Task Manager

I think it is a VFP 8 issue -I add some code after your READ EVENTS below.

>To all,
>
>I've deployed a couple of small EXEs on a Win XP machine. Here's the Main.prg:
>
>*********************************************************************
>* NOTE: Adding a config.fpw with "SCREEN = OFF" makes this redundant.
>_SCREEN.Visible = .F.
>
>SET DELETED ON
>
>SET DEFAULT TO ADDBS(JUSTPATH(SUBSTR(SYS(16), AT(":", SYS(16) )-1)))
>
>DO FORM frmMyApp.scx
>
>ON SHUTDOWN QUIT
>
>READ EVENTS

 CLOSE ALL
RELEASE ALL
CLEAR ALL
CANCEL && This makes sure your VFP IDE doesn't close if you are testing

>
>*********************************************************************
>
>The ON SHUTDOWN should end the EXE and pull it from system memory, but it doesn't. I first noticed this when I tried to rename the EXE and the OS wouldn't let me. I inspected Windows Task Manager and sure enough the bugger was still in memory. I killed it with Task Manager, but I need to know how to well and truely end the app.
>
>TIA,
>Thom C.