A couple of months ago I worked on an Access app that required a tree view.
The tree information had to be stored within the tables. In the end the
principle I used should be easily transferred to your tree view.

If you have a TTree object with TBranch objects within then the branches
only need to know their parent branch. Some checking is required to ensure
that you don't end up with a circular reference and that atleast one TBranch
does not have a parent so it can default to the TTree. The TBranch could
also have a sequence number for where multiple branches have the same
parent.

The TBranch would then have a string list of fields to be displayed and the
KeyField.

Or did I over simplify matters?

HTH

Shane

----- Original Message -----
From: "Paul Gallagher" <paul@...>
To: <IBObjects@yahoogroups.com>
Sent: Monday, January 29, 2001 4:42 PM
Subject: [IBO] TreeView again


> I see no real good way of creating a TreeView, that will automatically
display master/detail/detail/nnnnn data.
> I'm sure it can be done, but it is way beyond the scope of my project and
my skill level. Its not much different than trying to build a multilevel
grid. I think there is one out there, but it is quite complicated. Anyone
that needs that kind of functionality, is probably better off just
hardcoding it into their app with a standard TreeView.
>
> I am going ahead with my original plan of a single structured table. Its
what I need, and it is by far the easiest. This is how the TeeTree, and all
the rest work, as far as I know. My version of the IBO-aware VirtualTree,
will also be read-only, at least in the beginning. Moving nodes around just
doesn't seem real practical yet either. This is all stuff that can be added
later, if its needed.
>
> Also, I want to add some facility for multiple columns. Initially, it can
just be coded into an app, but it would be nice to have the tree grab the
data from the pre-defined columns automatically. Right now, there are 3
columns ParentField, KeyField, and ImageIndexField.
>
> Paul Gallagher
>
>
>
>
> [Non-text portions of this message have been removed]
>
>
>
>
>
>