>
>Yes that is what I am doing but in some cases the parent level can have >several thousand nodes. Since there is no load on demand feature I am forced >to load the entire parent node collection and thus the slow speed.
>scroll to the nearest match.

Simon,

PMFJI - but one solution is to create another level heirarchy above your current parent node. For example - I once I had a tree-view that showd vendors, then open PO's under them. I soon had way too many vendors - so I created a node above it and grouped them alphabetically by name like "A vendors" , "B Vendors", "C Vendors" etc. This worked very well.

Just a thought,