Hi Michelle,

Is it really necessary to have all the nodes populated?

It's pretty unlikely that ny one user would want to see >, say, 100 in any one viewing. Even if you increase that by a factor of 100, you're still well under the limit.

You could load the top level nodes and put a place-holder node under each of those top level nodes that has children. When a node is expanded, check to see whether it has the placeholder node and if so, remove the placeholder node and load the child nodes, along with a placholder node under each of the child nodes that has children. Repeat ad-infinitum.

If you need to, keep a counter of the number of nodes currently popluated and take some action if it gets towards the 64K limit.

This technique could have the added effect of making your application appear much faster as only the data that are required are loaded into the tree.

Cheers,

Andrew

>I'm having a problem with adding more than 65000 items to the ctTree control by DBI. The problem is that they use an array to access the nodes. This is a problem when I want to add more than 65000 items because I hit the VFP array limit. I can add the nodes, but trying to set any properties needs to access the array and then it crases. They consider this to be a bug in VFP and there's nothing they can do about it.
>
>I can work around most of it by relating their listindex to a cursor and storing info there, but I hit the wall trying to figure out how to change whether an item is checked or not. I don't think it can be done.
>
>So I'm wondering if anyone either knows some trick I'm missing to get it to work, or knows of a treeview control that doesn't have this limitation.
>
>Thanks,
>
>Michelle