>1. ON ERROR < do a valid command, function or procedure call >
>2. ON ERROR
>3. ON ERROR *
>
>#1 turns on an error handler which you've written yourself
>#2 turns off your custom error handler and returns to the default VFP error handler
>#3 tells VFP to do nothing in the event of an error (i.e. don't use the default VFP handler, and don't use any custom one either)
>
>Maybe what you were seeing is the effect of a #3 call rather than a #2 call? If so it can be dangerous and should be used sparingly, if at all.

Actually, if there are no errors at all for a while, think of #3 and check. If it was set, advise everybody to get scared first, then turn #2 or #1 on, run again, and wait for the avalanche.