How are you deciding what records are associated with what hierarchy level?

In order to use a treeview, this must be clear.
So in your sample table you would seem to need a "Level" (or group) field...

At this point I have not used a "level" type field but rather been hoping to convince Access to check each level to see if there are any children (lines with the ParentID set to me).

Do I need another field to specify the level?

OK, but still...

In your example how are you determining what records go in what level?

How many levels deep might your tree go?

I don't see a parent/child relationship in your table that would define which nodes belong where in the tree.  From the data you provided, I would have put them all on the same level.  To do this properly, you need another field (I usually call it ParentID) and the data would look something like:

ID   ParentID    Drawing#
1                         A10000
2           1            A10001
3           1            A10002
4                         A10003
5           1            A10004
6          5             A10005
7          5             A10006

If you want to do this in a report, the only way I know to do so would be to create a report based on the first level of your data (ParentID IS NULL).  Then create a subreport where the Criteria is (ParentID IS NOT NULL).  Embed that subreport in the Detail section of the main report and create a Master/Child relationship between the ID value in the main report and the ParentID in the child.  This would get you the 2nd level.  

Then, you would need to embed that subreport in the Detail section of the subreport again to get the next level of the "tree".

fyed,

Yes, that is what was confusing me as well...

I'll leave this to you as "Treviews" are not my strong point...
(I'll just monitor)


I only knew that in this case there was no way to determine what records went in what level...

Michaelj42

Tree Views seem to be the hot new design topic here lately...
Just a point that Treviews are really designed to show "top level" Hierarchy, ...they are not really designed to show all the way down to the "Detail" level (which is what you seem to be wanting)

For example, a Treeview would be best used to show data like this:

United States
    Texas
        Dallas
            Lewisville
Europe
    Spain
        Madrid
    Italy
        Rome


However, it is not well suited for data like this:
Cust107
    Cust107Order15
        Order15DetailLine1
        Order15DetailLine2
        Order15DetailLine3
    Cust107Order16
        Order16DetailLine1
        Order16DetailLine2
        Order16DetailLine3
        Order15DetailLine4
        Order15DetailLine5
...because the number of detail lines can vary greatly
(which is what you seem to be wanting to display)
For data like this, there are Access tools like:
Subdatasheets
Main/Sub Forms
Grouped Reports
...that will do a better job of displaying this "One-To-Many" type data.


Another example would be a "Select Folder" Dialog box.
Where only the *folders* are displayed (not the records inside each folder).
Make sense?

Finally as "cool" as a treeview might seem to be, they are not easy to code, and can end up being fairly complex if you need modify the *Nodes*/levels

JeffCoachman

Thanks for the input guys.

Basically I just wanted some way to document and display for informational purposes the layout of various assemblies to guide the guys doing quotes as well for information to the production guys.

In my thinking, the treeview was a good way to graphically represent this, but I'm open to changing my mind :).

I was just hoping to throw the idea out there looking for some guidance on how to proceed or for ideas from those of you who know Access inside and out.

I've been looking at this guide and working through the episodes. There sure doesn't seem to be much info on these ActiveX controls, or am I just using the wrong keywords?

fyed: I have seen 3-4 levels deep.

JeffCoachman: I am not insisting on using treeview, so yes, the real question is what is the best way to represent this data. This is just a low priority idea I've had for a while. I recently tried to start putting code to the idea and I got stuck :).

I also read here which seems to do pretty well what I had in mind.

I guess the answer to how do I represent the level of a particular datum is "I don't know..." ;) So far this isn't a lot more than a twinkle in my eye.