>Mark,
>
>I believe the problem is when vartype() is asked to determine the type of a property for a non-existant object. I believe that it was said that it is by design because vartype() was added to be faster than Type() and therefore is doesn't do the checking the same way and it therefore cannot trap the non-existant object.
>
>All fo this is from memory, so it may not be correct.

I created a form object from the command window, and tested it against an undefined form property [? Vartype(oForm.Test)]. It did return U. I have not had a chance to test this under runtime only, but I will later this evening.

Now, if I set oForm = .null., and test for oForm.Anything, I get an error returned. But Vartype(oForm) will return X at that point.

Or am I missing your point?