>>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.
>
>So it only appears to be a question when (VAR)TYPE = "O" ? Good, cause I'm not using it for that.

TYPE is reliable. I don't know why I allowed myself to use both.

>
>>Why are there letters on the Franklin Mountains?:-)
>
>Different letters for different reasons. The only one I know specifically is the M for the local college team, the Miners.
>
>Chris.