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

Maybe it's a good time to refactor the error handling routines, especially in view of TRY...CATCH. It's my belief that there are some common errors that could eliminated (i.e: "File in Use") from the general error handler, and dealt with in a more graceful manner.