Again, the problem is that all this control exposes in an Index value, which changes any time a node is inserted
before it.

The help file that I have only shows sequential expamples. They don't show an example of a node being added
before an exiting node.

I sent a support message to DBI, they wrote back, and I reponded. We'll see what they have to say, although
I don't foresee any easy solution.






>It looks like you if the treeview is already built, you would need to select the parent node first (make it the selected node) and then add the child. Look at Adding Nodes to the control and adding nodes as a parent node is expanded in help there are more examples there.
>
>
>>I thought of that, but then I would have to iterate through the entire tree from top to bottom looking for the
>>PK value. There doesn't seem to be any alternative though.
>>
>>With a standard ActiveX TreeView control I could do:
>>
>>

>>oNode = .TreeView.Nodes(parentkeyvalue)
>>.TreeView.Nodes.Add(oNode.Key,4,NewChildKey, 'Child Text)
>>

>>
>>But the DBI control doesn't seem to support the typical collection syntax.
>>
>>It's sort of disheartening since I paid $400 for the set of controls and I find out they don't follow standards.
>>
>>
>>
>>
>>
>>
>>>I have added a series of nodes to the tree. I then want to go back and add additional nodes as children of pre-existing nodes.
>>>
>>>Use the Node Cargo to store the primary key of from the underlying data and use that to find the child records.