Page 2 - Example code for treeview control populated from DB2 tables

The order for my treeview control did not post correctly. I want to allow the user to select a DATA_CLASS_NM and then the SBJCT_AREA_CATEG_NM's for the selected DATA_CLASS_NM will appear. Then they will select a SBJCT_AREA_CATEG_NM and then the SBJCT_AREA_NM's for the selected SBJCT_AREA_CATEG_NM will appear. Then they will select a SBJCT_AREA_NM and the ENT_NM's and ATRBT_NM's will appear where they can select whichever they want to and then I want a web form to appear with general information about the ENT or ATRBT they selected. I hope this makes sense! Thanks!

The code that I wrote is recursive in nature, thus allows for multiple child nodes. You can have children of children of a child node, for example. I'm not sure how this will work with your current table structure, but I'm sure we can figure something out.

Next, what I need from you is a couple sample records for each of these tables.

Finally, I need to know how each of the fields will be used with the treeview control. My example, uses the following:

itemid (autonumber record identification), parentid (the id of the current records' parent record), linetext and lineurl are used for treating the treeview nodes as links which will direct a user to another page. linetext would be the text that would display in the treeview and linurl would be the URL that the link would take the user to. By the sound of it, you're not using as a link, rather as a postback that would return a desired web form based off of the selection.

You are exactly right. I need to allow the user to go through the treeview control and once they get to the Entity Names or Attribute Names then they can select one to display a web form that shows fields from a bunch of different DB2 tables. So, in other words, whenever an entity name or attribute name is selected, it will display a web form with general information about what was selected.
-----------------------------------------------------------
DATA_CLASS table:
DATA_CLASS_ID DATA_CLASS_NM
1 Agreement
2 Incident
3 Compensation
-----------------------------------------------------------
SBJCT_AREA_CATEG table:
SBJCT_AREA_CATEG_ID SBJCT_AREA_CATEG_NM
1 Customer Agreement
2 Individual Agreement
3 Event
4 Incident
5 Claim Information
6 Service Information
7 Compensation

SBJCT AREA_CATEG_ID DATA_CLASS_ID
1 1
2 1
3 1
4 2
5 2
6 2
7 3
-----------------------------------------------------------
SBJCT_AREA table:
SBJCT_AREA_ID SBJCT_AREA_NM
1 Agreement Contract
2 Agreement Accounting
3 Billing
4 Calculation
5 Health Evidence
6 Enrollment Event
7 Incident Event
8 Management
9 Payment
10 Service (Core Information)
11 Rep Compensation
12 Sales Credit

SBJCT_AREA_ID SBJCT_AREA_CATEG_ID
1 1
2 1
3 1
4 2
5 2
6 3
7 4
8 5
9 5
10 6
11 7
12 7
-----------------------------------------------------------
ENT table:
ENT_SURGT_ID
ENT_NM
SBJCT_AREA_ID
-----------------------------------------------------------
ENT_ATRBT_RLSHP table:
ENT_SURGT_ID
ATRBT_SURGT_ID
-----------------------------------------------------------
ATRBT table:
ATRBT_SURGT_ID
ATRBT_NM
-----------------------------------------------------------
So, as an example, I select Agreement on the treeview control; Customer Agreement, Individual Agreement, and Event would appear under it. I then select Customer Agreement on the treeview control; Agreement Contract, Agreement Accounting, and Billing would appear under it. I then select Billing and both attribute names and entity names would appear on the treeview control that are associated with Billing. Once an entity name or attribute name is selected, the web form would appear with general information about the path that was selected in the treeview control. I hope all of this makes sense! The ENT table, ENT_ATRBT_RLSHP table, and the ATRBT table have not been populated with values yet so I do not have any values to list. These tables work in the same way that the other tables do; however, both the entity name and attribute name are on the same level. So, you do not have to select an entity to get an attribute or select an attribute to get an entity. You can select either one, depending on what the user wants to see, and from there a web form is shown. Please let me know if you need anything else from me! Thanks!!

Okay, I see...You have a standard relational database setup (that's a good thing )

It will take me some time, because I'm always busy, but I'll see if I can come up with something that will work for you

If entity and attribute are on the same level, then why do they have a relationship together? Is that for other purposes or does that need to be incorporated into this menu?

The relationship needs to be incorporated into this treeview control! Thanks so much!!

Explain how it should be incorporated...if these are the last elements in the treeview, what effect does their relationship have on it?

Entity means table and attribute means column. From the ENT table to the ENT_ATRBT_RLSHP table there is a one to many relationship. From the ATRBT table to the ENT_ATRBT_RLSHP there is a one to many relationship. I am not sure on values that are in these tables because I am not creating them. I am still a little confused on what these tables actually are. I am not sure if this is what you were asking so let me know if you need more info from me. Thanks!!