>In most cases (or at least in my cases), the treview simply provides a pointer to table data. I typically store the table key (or some facimile) in the treeview's KEY proporty during the add method. When the user clicks a particular node, the length of the key may help signify it's place in the hielarchy, ex: A root node would have a 'shorter' key than a child node, a child may have a shorter len(KEY) than a grandchild, and so on. It may be helpful to what your doing to read, or store raw data (from) to a table or cursor, and simply use the tree view to reference the table. In this case, your solution would print from the table, rather than the nodes text reference.
>
>

Hi Terry,

In my case I cannot print from table because the table will not be in the same order, don't ask me why I have done but there is a purpose for this :-)

You have a good point on appending parent's key to child nodes. I will try that. It would be handy in scanning the nodes later.

Regards