As volume of data increases, it's taking longer and longer to load my
TreeView.
Currently7 takes about 2.9 seconds to load a tree with 2,176 nodes.
If the Node.Add coding is rem'd out, the time drops to 1.1 seconds...
so I see about 1.8 seconds to work on.
Eventually the data will probably be well over 10,000 nodes - maybe ven
20 or 30... so we definately have a problem.
I'll worry about the 32k limit when it comes...-)
Right now, I'm just iterating thorough a work table, adding
node-by-node with .Echo=False.
A little Googling turns up references to loading trees from some other
data structure to gain speed - but it seems to apply to .NET trees and
not to MS Access TreeViews.
Have I got that part right?
Can anybody offer any tips in minimizing the processing time when
loading an MS Access TreeView?