>Hi
>
>I've installed an on error routine in an application.
>
>Its an old app that has a lot of errors and users are used to ignoring them. I've put in an ON ERROR routine so I can log the errors and iron out the worst offenders.
>
>In the on error routine I give the user the choice of carrying on or quitting.
>
>If they select quit I
>
>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 ?
>
>Nick

This may not solve your problem, but it seems to me that the QUIT command is at the wrong place. You might not need it at all. Consider the READ EVENTS as a kind of "main loop" (an infinite loop) in your program; CLEAR EVENTS is used to break out of this loop. While the READ EVENTS is in effect, VIsual FoxPro will wait for user input, react to it (for example, in a button's Click() event), then go back to the READ EVENTS to wait for more input. When a CLEAR EVENTS is given, Visual FoxPro "breaks out of the READ loop", and continues with any cleanup commands you have after the READ EVENTS. A QUIT command is not even needed; but if you have one, I would expect it to be somewhere after the READ EVENTS command (immediately after, or after any desired cleanup).