>>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...

Hi Thomas

have you got an example.

I may try putting a clear events before the read events in the application.

Thanks