FYI - I'm using otree.object because that's the only way to truly disable the treeview we've found.
otree.enabled = .f. does not work - you can still click on nodes
otree.object.enabled = .f. locks it up just as you would expect
Ken
>Ken,
>
>Can you show the code that is actually erroring out?
>
>The only time I ever use .Object is to make sure the right property gets accessed for conflicts with VFP PEMs.
>
>
oTree.object.XYZ =
>? oTree.object.ASD
>
>I don't know if you can actually do something like
>
>
oX = oTree.object
>oX.ABC =
>
>>I am having a strange situation where if 'oTree' is a reference to my treeview control, 'oTree.object' is returning a reference to the first NODE object in the treeview rather than the treeview object itself.
>>
>>Any ideas why/how this could be happening?
Ken B. Matson
GCom2 Solutions