>That behaviour is what I've observed as well. Actually, I maintain that Vartype/Type should not create an error 12 at all (not even passively as in this instance) since this is part of what is being tested with Vartype/Type. How to handle the situation of an non-existant variable should be left up to the individual developer.
>
>Richard
>
Hi Richard, et.al.,
I agree. My thinking has been cleared up, (I hope), by the responses. AERROR is fine; it's VARTYPE() that is dropping info into the some error structure when it shouldn't. TYPE() doesn't exhibit this behavior.
It would seem to me that VARTYPE() should never corrupt the error relics when no error has been raised. Further, I would be good if VARTYPE() didn't error on commands such as VARTYPE(xx,.t.).
Charlie