Thank you for the explanation. I learn something new every day. :-)

>>Yes, that why I added the smiley. Better safe than sorry! By the way, I have never heard the word vette, what does it mean?
>
>I grabbed it from some news speak I heard. My spelling is phonetic. I could not find the word as I spelled it in the dictionary.
>
>The context I hear hear in are cases where something requires (like a resume or a campaign contribution) assurances that what was presented was indeed the proper and within the rules.
>
>For example, Political Appointments are vetted to assure that the appointee's background is acceptable. Contributions are "vetted" to assure they meet the requirements of election law.
>
>For me to say that VARTYPE did not vette for objects, is anotherway of saying that VARTYPE did not do a proper evalutaion of the subject (argument) it was passed. Or - VARTYPE does not work as advertized.
>
>Hopefully someone will pop in and correct my spelling. I know that MS Word allows it, by my paper back dictionary don't define it.
>
>Vette is short and for "checking and verifying a representation". It this object.name really an object? Etc.:-)
>
>>
>>>>Hi Terry,
>>>>
>>>>For your information (or you may already know this), VARTYPE is faster than TYPE. But, of course, I guess you will never notice the difference in practice. Unless you use TYPE extensibly. A nanosecond here, a nanosecond here, before you know it your aplication runs milliseconds faster! :-)
>>>>
>>>
>>>That may be true, but VARTYPE is inconsistent. Sometimes it vettes and sometime it don't. I'd rather be a little slower, and not crash, than a little quicker and fail:-)
>>>
>>>>
>>>>>I started using TYPE with OCX controls because VARTYPE did not vette OCX objects in the circumstance I was using them.
>>>>>
>>>>>For example:
>>>>>IF VARTYPE(Myform.MyTreeView.SelectedItem.Key)==[O]
>>>>>would ometime crash inside VARTYPE, with the message 'is not an object', or fail after the question was asked (VARTYPE passed), when the [really] didn't exist.
>>>>>
>>>>>TYPE has never failed (for me yet). For foundation classes, I still relied on VARTYPE:
>>>>>IF VARTYPE(MyForm)==[O]
>>>>>But since moving to 8, I recall that these little issues popped up when a VARTYPE was nearby.
>>>>>
>>>>>I don't know if there is an issue with VARTYPE. But, I do know that my issues are greatly reduced by using TYPE instead.
>>>>>
>>>>>Mark noted in this thread that he noticed VARTYPE was unresponsive (and may have adversely affected internal reference) when he was resolving some PEMSTATUS isses.
>>>>>
>>>>>I saw it to in a Combos interactivechange!
>>>>>
>>>>>The symtom: Was first pass at a method went okay. But once the VARTYPE was encountered, subsequent firing of a controls method did not produce an action.
>>>>>
>>>>>Why are there letters on the Franklin Mountains?:-)
>>>>>
>>>>>
>>>>>>>I wnt back to the code after I changed the vetting from VARTYPE to TYPE and noticed my changes were incomplete.
>>>>>>>
>>>>>>>One of the vetts read: IF VARTYPE('SoAndSo')==[O]
>>>>>>>It should have read: IF TYPE('SoAndSo')==[O]
>>>>>>>
>>>>>>>I changed it and got a reprieve. I quite using VARTYPE with activex because vetting was inconsistent. I will problable rephrase all my object vetting from VARTYPE to TYPE.
>>>>>>>
>>>>>>>Other little issues (non OCX) I've had in VFP 8 have were local to a VARTYPE vette. Maybe the same justification for not using VARTYPE with OCX needs to be applied to other object vettes.
>>>>>>
>>>>>>Are you saying there are known issues with using VARTYPE? I'm using it to verify passed parameters in several places. I'd hate to see it bite me...
>>>>>>
>>>>>>Chris.