>>CLEAR EVENTS
>>QUIT
>>
>>But sometimes when the users select quit they get Cannot Quit Visual Foxpro.
>>
>>I suspect there are paths through the system that may issue another READ EVENTS. Could this cause the problem above ? Are READ EVENTS nested ?
>
>As saving any state or logging out/off seems unimportant in the above,
>sending a KillProcess via WinAPI is usually faster and less prone to such behaviour...
Hmm, if there are VFP tables/index files open, they could get damaged that way. I'd use that only if all other methods have failed.
Regards. Al
"Violence is the last refuge of the incompetent." -- Isaac Asimov
"Never let your sense of morals prevent you from doing what is right." -- Isaac Asimov
Neither a despot, nor a doormat, be
Every app wants to be a database app when it grows up
