Figure #1 Note: It doesn’t matter if you use SQL Server 2005 or a previous version to try this sample.
Then, we have Tree View page with the Tree View control declaration as follows. I have been trying to 'mod' it a bit to suit my purposes.
what you could have is a link or path to a selcted item in the database.
Then you should use the value that is returned to lookup the column in the database where the path to the specific file is.
Certainly, there’s room for creating a hierarchical data source control to deal with this so that data access wouldn’t require that much code; however, I believe that getting your hands in code is the best way to learn about the technology.protected void Page_Load(object sender, Event Args e) private void Populate Root Level() private void Populate Sub Level(int parentid, Tree Node parent Node) protected void Tree View1_Tree Node Populate(object sender, Tree Node Event Args e) Great work and I see that it is still helping people after 6 years.
Microsoft has developed it based on feedback which arose from the release of the Tree View control in the open-source IE Web Controls package, targeted at the previous version of ASP. Tree View has not just been rewritten; it now also includes a major set of new features such as support for client-side populating, on-demand populating, postback events, hyper link navigation, and a lot more. Listing #1 This means that we are setting the initial expand depth of the Tree View to the first level of nodes. I want to ACTUALLY display a mother (parent) with all her children on her SPOUSE' S page, and if that man has more than one wife, display all the wives with all their children. The problem is for my purposes that the sub proc actually works too (thank you, will use it elsewhere) BUT since I'm working with genealogy, I really don't want all those children-of-children-of-children coming from the database. We want to use the client-side node populating feature so that we can provide our users with a better usage experience. We also want to show lines between the nodes and the expand/collapse icon if our tree nodes have child nodes. Listing #2 This happens by connecting to the database, querying the first set of nodes (having null as the parent id), and creating Tree Node objects with the Populate Nodes routine, which follows next. The Populate Nodes method iterates through all rows in the Data Table, and if the given node has child nodes, it sets the Populate On Demand property of the Tree Node object according to that. Is there a way to rearrange this so that not only does only one parent with their children (or 2 spouses with their children) display without actually going to the db and GETTING all those leaves and twigs? The only thing I need to do is add a column to mine with the navigate URL string since I'm using the Tree View as my menu for my website. Paul Sql Command obj Command = new Sql Command( "SELECT id, description, (SELECT COUNT(*) AS Expr1 " "FROM navigation_list " "WHERE (parent_id = sc.id)) AS childnodecount " "FROM navigation_list AS sc " "WHERE (parent_id = @parent ID)", obj Conn);and you should close your connection on each request..Conn. Close();thank you your code very very very help me and i want to thanks of you bundle and bundle thanks because i was confused about this and finally i solve and issue from your code. thanks alots.hi, I tried this only root node is coming. I had to enclose the content[not the using statments] of the code behind page in a namespace where the namespace was the project name. Have been looking for a way to do 3 level menus for a while, as I had found some code that could do 2 levels, but wasn't easily adaptable for 3 levels.