Justok,

First thee are two VFP errors for which your erropr handler will not be called , they are insufficient memory and do level nesting too deep. The first won't call you error handler because there is no memory available to call it, the second because all of hte calling stack is in use and there is no call level availablke to call your error handler.

That said, you need separate the VFP errors from the operating system errors, tyhe error you displayed is anm OS error and not a vfp error. VFP errors are alway seen in a message box with the Cancel Ignore Suspend options. If t6he error is in any other form then it is not from VFP.

Thirdly you error handler always returns a value, to what? Who do you think is going to receive the value returned by your error handler and what is going to be done with the value?

Oh yes, the one other place where the default VFP error handler will be called is when there is an error in your error handler.