Thanks for checking the code and affirming my superstitions regarding VARTYPE issues regarding object vetting.

I think I stuck with VARTYPE is some cases just so I would not have to place quotes in the parameter argument. But as I look back to other V8, they were all local to a VARTYPE. I did work arounds with proxy names (even feared invisible characters in my source code!).

And - all that just so I would not have to enter quote marks! Is that lazy or what?:-)

I am releived that it is working. I only tested the first pass on the interactive change. VARTYPE (even in 6 and 7) did not vette OCX properly.


>>I also note that VARTYPE does not vette OCX objects. For two years (or so) my code has been vetting OCX exclusively with TYPE. I maintained VARTYPE for form vetting. But in 8, VARTYPE is not as reliable as it was with 7 or 6 - at least that's what I think I am seeing.
>>
>>I've other issues with VARTYPE that I tried to solve with proxy names for forms and so on. They worked. But now, I suspect, that I can revert to actual object names by simply switching to TYPE.
>
>Got it. You can also have a problem with PEMSTATUS with ADO objects [and I suspect some OCXes]. The first time you try to test for a PEM with PEMSTATUS, you get a False return value even though the PEM does exist. The second time you hit it, you get the correct return value. However, if you use TYPE function, it works all the time.