I am not sure, but perhaps you should include a CLEAR EVENTS. In other words: Your ON SHUTDOWN invokes a function, which may include CLEAR EVENTS, QUIT, and perhaps eventually some additional cleanup before the QUIT.
>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
>
>*********************************************************************
>
>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.
Difference in opinions hath cost many millions of lives: for instance, whether flesh be bread, or bread be flesh; whether whistling be a vice or a virtue; whether it be better to kiss a post, or throw it into the fire... (from Gulliver's Travels)