THE TYPE() is working for now. VARTYPE is still in the air. The reason I got the failure is that one of the vettes (there's a small list of 'is it an object', TYPE('SoAndSo') was in fact VARTYPE('SoAndSo') - note the qutes. I removed the 'VAR' so it read 'TYPE' and it is working.

I always use TYPE when vetting an ActiveX - and (till now) have been using VARTYPE for form objects.
Go figure - thanks for your kind advice.


>>What is the status (if any) of a VFP8 SP2. I am spending a lot of time inventing clever work arounds to prevent leaks in some of the more straight forward action methods.
>>
>>Example:

>>If VARTYPE(SoAndSo)=="O"
>>   SoAndSo.Value="New Value"
>>Endif

>>I just had an incident where VFP error manager told me SoAndSo "is not an object" at SoAndSo.Value="New Value" , even though VFP vetted the test (in the line before) as true!
>>
>>I will admit this much:
>>SoAndSo is a form name, as well as a PRG name and a DBF name!
>>
>>Should I go back to 6?
>
>You could always test
>

>TYPE('SoAndSo.Value') = "C"
>