That did it! That's why I stopped banging my head against the monitor and just asked....

Probably you never saw it do this because in trees you've used the event that happens when clicking on a node completed quickly enough that there wasn't time to fire another event. If you want to see it happen, try putting a delay (say, 1/10'th sec) in the NodeClick event, then use the arrow keys to navigate the the tree (the right arrow goes "into" a node, which causes a NodeClick to fire)

>Can't say that I've seen that on the Trees I've worked on, but anyway...
>You might want to try ThisForm.oleTREE.OBJECT.ENABLED=.F. (note the "OBJECT" keyword reference)