Hi Nancy,

How is my favourite driver doing? < s >

>In the case that bombs I'm not sure, but perhaps your trapping code does something that really crashes your code. You'd need to tell us what line of code causes the crash and what the error message is.

I have seen this happening in the framework that I use (Visual Promatrix).
One developer used the pessimistic buffering too and when he pressed ignore, VFP would do a CLEAR EVENTS by itself, which exited the application.
When you would generate the error using the ERROR command, the complete error routine works as advertised and no CLEAR EVENTS is issued, so I think this is a VFP bug.
The workaround was to create a semaphore (in my case it was _SCREEN.oApp.lExitApplication, which defaults to .F.) and use the following code where the READ EVENTS is issued:

DO WHILE !_SCREEN.oApp.lExitApplication
   READ EVENTS
ENDDO

At the place where the 'real' CLEAR EVENTS was done, I used this code:

_SCREEN.oApp.lExitApplication=.T.
CLEAR EVENTS

hth,