>>Like I said, this was sometime ago, so I don't know (and haven't tested) if it still applies. I believe, however, that it probably does.
>
>Yes... it still works that way... also, with AND expressions, once a .f. is hit, it stops evaluating the expression... this is why you can do...
>
>if vartype(oObject) = "O" and oObject.Property = whatever
>
>If the first half is .f., and it DID try to eval the next expression, you would get an Object Not found.
>
Hi BOb,

Of course! Don't know why I didn't think of that. Maybe I'll chalk it as "a hidden dangers of OOP". You subclass, encapsulate and then forget the underpinnings.< rbg >

Regards,