Hey Perry!

I can handle the trap part, but how do I turn around and send the non-trapped error to VFP? I thought of RETRY, but then it comes back into my routine. I could turn off my routine ('ON ERROR'), but then it's lost for when I want it the next time, right?

I know this is easy, but I guess I haven't had enough coffee today.
-- John


>All you need is a:
>
>Do case
>Case Myerror = nnnn
>
>
>section in your errorhandler.
>
>pf
>
>>Okay, you'd think I would have hit this one by now, but I haven't... and it can't find it in the archives:
>>
>>Is there a way to trap for one specific error (1542, 'Base Tables changed' in this case), and if it is NOT this error allow standard VFP error handling to continue, otherwise run a routine (DBC rebuild routine in my case)?
>>
>>Thanks in advance. I know this one is probably really easy.