Hi!

We usualy populate the tree on demand. This means that we do not populate child nodes in tree until parent node is expanded. We add only one empty node instead to show the + sign for exanding. When user expands node, we remove that empty node and add child nodes. Usually child nodes are from the query. Above approach works well only when you have very good splitting of your data in tree to parent/child nodes (well-categorized data), so you will not have much child nodes for each parent/ For example, list of offices -> list of warehouses for office -> list of choises of information for each warehouse (employees, items, invoices etc. etc.) -> list of invoices -> list of items in invoice (each '->' represent parent-child relationship in tree). No need to fill te tree with all information. Just fill on demand - usually most information will still not be viewed by user.

HTH.

>Hello,
>Im using a treeview control as part of the user interface of my app;
>i noticed a few things with it, when i check/uncheck any node, the whole tree refreshes and its pretty slow most specially when there are lots of nodes in it,
>is there any way around this? subclassing?
>
>thanx,
>Benj