It seems (almost) simple if I understand your proposal.

You envision a tree with main nodes. The number of nodes will vary.
We should set aside the treeview issue - that is fairly staight forward. It seems the main issue is "How to address multiple, yet unknown edit entry points when a tree root is selected.

This routine demos a methos to do that. You would have to dock a form or container inside the form with your treeview, the, when a parent node is selected, and a container with appropriate controls for each child and populate those controls with revelant data from your DBF.

This code offers one way to solve for a vaiable number of data items (treeview child nodes) that would need to be made available for edit. The containers only have edit boxes but textboxes buttons etc could also be added

Let me try in another post - my paste was loosing CRs

>Hi all
>
>Has anybody seen TreeLine outline utility? http://www.bellz.org/treeline/index.html
>
>It has a treeview and each and every node has the facility to be clicked on and configured. This configuration allows similar node to use the same settings of fields, thus nodes a, d and f of type default will have 3 text cum edit box, and nodes b,c and e can have a type of say custom and this can have 1 text cum edit box, 1 date field.
>
>I am interested in how this kind of data fields handling can be done in VFP, as we don't know what the user is going to select for fields.
>
>Hope I could explain in words my thoughts.