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

I've had a situation in FPD2.6 where an indexing routine was called from OpenIt() function's error handler (when it reported bad index and some other errors), then the indexer had an error handler of its own, which fired if the table was corrupt. It never fired - the error handler called the indexer again... though not indefinitely (because I watched it in the debugger, and broke its neck).

I've found a fair and neat workaround (setting a variable to the error code in the error handler, and later checking for it after the USE statement (when error handler already exited), so the indexer didn't get called from the error handler, but directly instead), but I just wander if it will behave differently in VFP. Any experience on this, anyone?