Also, I'm wondering about the loadondemand property. If it is automatic, the documentation says that it will load data when the page loads. Then, if that is the case, why even use it? I thought the whole point was to only load data when a node is expanded and there are child nodes below it. It also says that manual will only load when user expands a node, so shouldn't it be true or false then? Unless, the documentation is missing something important?
Both "Automatic" and "Manual" settings for load-on-demand are triggered in the same way. The root-level nodes are loaded on the initial page load, and when a node is expanded and doesn't yet have any child rows, a postback is triggered to retrieve child rows. They differ in the following ways:
In short, "Automatic" does the plumbing for you, while "Manual" gives you more control.
Thanks Vince. I already had my tree setup with binding for each level. But, now I find that there are more than one relationship between some levels of the tree, so I think that manual load on demand would work better? But, since I already have bound 3 levels and want to add a 4th level, what would be the best way to move this code to manual load on demand? I'm just assuming that manual load on demand would load the tree faster than binding? I simply call my 'loadtreedata(...)' method when I want to refresh the tree, as the data is always changing in the database, and it has to be refreshed very often, and with about 100 nodes, it's slowing down, as of course it's loading everything at once.
Is there some extensive sample code for load on demand manual? I have 3 datasets, corresponding to 3 levels of the tree.
Thanks