Fred,

I found it!! I was using the foxpro application wizard, it created a config.fpw in my application folder. It had the command SCREEN = OFF.

There were some posts that Ed Rauh had replied to years ago where he advised to check for that. I didn't even realize I had this config.fpw in my application folder.

SCREEN = OFF = disaster (for me at least)

I need to look into what this is designed for, but in the meantime, obviously I need to get rid of it!



>Are you sure you're ever getting to your UNLOAD code?
>
>
>>Fred,
>>
>>I put it in the unload, so the form won't close until I click the close button. Even when I have no clear events whatsover, the application still exits, but the process remains alive
>>
>>Thanks
>>
>>This works from within VFP..
>>
>>>>Help - I know I've done this countless times before.. but.
>>>>
>>>>I have the simplest program:
>>>>
>>>>*simpleform.prg
>>>>do form simpleform
>>>>read events
>>>>
>>>>compile the exe
>>>>from command window
>>>>do simpleform.exe - works
>>>>the only thing in simpleform, at all, is clear events in the unload.
>>>>
>>>>** this works fine
>>>>but when I run it from the command line, the program exits, but, the process simpleform.exe is still active under processes in task manager (the application is gone)
>>>>
>>>>I have to kill the process to get rid of it.
>>>>
>>>>What am I doing wrong?
>>>
>>>Sounds like you just closed your form so you're stuck at the READ EVENTS line of code. You need to issue a CLEAR EVENTS at wherever it is you are closing your form.
>>>
>>>It may be as simple as adding the CLEAR EVENTS to your Form.Destroy method.