RIO maintains the DBF "object" and the tree "object" seperately but in sync.

IOW: A change made to the data presented in the data entry area - the textbox and save/delete buttons updates the DBF and treeview. The updates are synced - but the require their own discrete pieces of code. The goal as a developer is to make it appear as though it's automatic.

There are types of XML files called "manifests" that may appear as a tree object when opened with explorer. And we could make the connection that the XML to Cursor VFP features might offer some kind of automatic sync. I have worked with XML manifests - but I had to "crawl" through them with MSXMLDOM methods to move it to a treeview. I could not get the XML/Cursor features of VFP to work with the manifest (the manifests I work with integrate the contents of several table containers [cursors/DBFs]). There are also flaws (or issues with the DOM) that in some cases double up (for example an item tag can have a string between the tags and can also present in a straggler (the #text) node (maybe its an attribute).

RIO hopes to appear to have that automatic feature - but in reality it requires discrete (though not difficult) code to give that appearance.

The contents of a tree can be saved to a table, but we have to use the tree's node object methods to retrieve the stuff to write it to a table. Typically the information presented in a tree is [just] an outline. It might combine field data in the nodes text property - but the issue then would be parsing it to a discrete field based container like a DBF.

RIO maintains a [couple of] DBFs and uses the information in those DBFs to build the tree. Once RIO is exited - the DBF reamins - but the tree goes away!

RIO could be modified (change the labeledit property) so that a change could be made in the treeview and then forwarded to the DBF (much like changing a file or folder name in Explorer. If more than one field needed to be changed, then rio would need to have a node object for each field. There is also the memo field data - it would be difficult to to present memo in a tree for edit changes.

But with some work and a right click menu on RIO's tree, wht you are suggesting could be done. See the labeledit property.

>Hi All,
>
>Long time ago I saw one treview example being able to save
>treview content as dbf table. Anybody knows link to something like that?
>It was simple table with 3 or for fields...
>So you were able to build the tree and save it to free table and then
>load it up again into treeview.
>Is it possible with your RIO example ?
>
>Any input/link is appreciated :)
>Thks+++
>Sergio