Your assumption is correct. I wanted the nonexistent .Treeview property of an existing Node object. Since I don't have that, there are plenty of workarounds.

>I was working on the [maybe false] assumption that the nodes get created at some point with all the necessary information available, and it's later on when the nodes are referenced that he will want to know to which treeview they belong.
>
>If, on the other hand, he has a node creation funcion and wants to know the treeview as the node is being created, then yes, some other mechanism is required. It seems to me, in that case, that the simplest way is to feed the node creation method a parameter representing the treeview.
>
>Alan
>
>>>You could fill in the TAG property with the name of the TreeView object when you fill in the other information.
>>
>>But would not that require a reference to the treeview: oTV.tag?
>>
>>I was thinking maybe a form property?
>>
>>>
>>>Alan
>>>
>>>>If I have a node object, can I get a reference to the treeview object in which it lives? I was looking at the properties available for the node object and I don't see it.
>>>>
>>>>http://msdn.microsoft.com/library/default.asp?url=/library/en-us/cmctl198/html/vbobjnode.asp
>>>>
>>>>The .parent property and other similar properties all return references to other nodes in the tree.
>>>>
>>>>If there isn't a way, I'll live with it. I'll just pass the node and its tree in the function I'm writing. Less efficient, though.