>>AFAIK, this error does not affect how the Task Pane behaves. It's just that I was expecting VFP to startup clean with no initial error info.
>>
>>I was having a self-inflicted problem with a form where the error message returned by AERROR made no sense [the error produced by the Task Pane as it turns out]. So in my testing, I decided to quit VFP, restart VFP, run AERROR to make sure I had no VFP Startup errors, and BAM! There it was. I have had problems in the past where I got confused by AERROR because there is no way to clear the error info during a VFP session without having the Quit VFP to begin with. So, now when I debug, I usually issue ERROR 3 or some other bogus error [like ERROR 2] so I load VFPs error info with an error I know I am not going to get.
>
>You're pretty picky.< vbg > You know, I'd never really thought about it, but you're right, there's no way to reset the error state for AERROR(). Interestingly enough, however, is that ERROR() does reset by itself automatically.

ON ERROR ? ERROR()
>? "D" + 1 && 107 Datatype mis-match
>? 1 + 1 && No error
>? ERROR() && 0

The same technique, however, doesn't work with AERROR().

Hehe! My wife tells me the same thing [picky]. I prefer thorough. < bg > AERROR is so easy, but maybe I should just create my own MyAERROR function to populate or clear an array based on the value of ERROR() since it seems to be dependable. FWIW, MESSAGE() does not reset either.