Hello all.

I've been incorporating the Microsoft TreeView Control in a few different areas of our application through ActiveX. Everything seemed to be working wonderfully until testing of the system as a whole uncovered something that seems to be a problem resulting from the TreeView Control!!

Everyone remember how, with an older, slower system, or even with a CURRENT system that is SERIOUSLY bogged down where memory is concerned, entering info in a textbox could in itself be an annoying process for the following reason: say 10 keys were hit in succession, and the first 4 characters show up, then a few seconds later the 5th, then a few seconds later the 6th, 7th, etc.??

Okay ...

There is in particular a box in our app in which we've included an incremental search feature. BEFORE any of the components w/ the TreeView are run, this box works fine, with no such lag as above.

AFTER any of the TreeViews is opened, whether or not it's expanded, used, etc, and even if it's closed and the form in which it was contained is released, entering info in this box results in the type of 'lag' described above... and our Performance Monitor does show strange figures in CPU usage and Memory Allocation.

Is there a "deallocation" problem w/ the TreeView control? Should I actually "clear" all of the nodes before releasing the form, which SHOULD in and of itself destroy the tree??? Or is there some kind of 'compatibility' issue that perhaps is interfering with our incremental functionality in particular?

"What's going on??" ;-P

If anyone has any insight on this, I'd appreciate it! Thanks!!