Thanks I think I can get what I need now.

Simon


>Hi Simon,
>>
>>The listbox is my most used component because I use it instead of a grid. I think I will play around with the pictures as you suggested because I think I can find a way to make it work nicely.
>
>Just a hint: start with a 3 state as base and make 2 state a special case. And yes, having a picture is nice and virtually no "feelable" drag on perf.
>
>
>>I would be interested to know what you did to speed up the treeview. I played with it several years ago but stopped because of the slow speed. I modified my listbox control to work as a treeview instead and I have been using it that way ever since.
>
>The main problem there was a lousy integration into their own framework, which itself was not written by perf experts. They used the dbi-controls and the dbi tree could get "raw" loading of > 5000 items/s on the machines used back then (still PIII). I cut through most of the framework stuff to create a TV control with the basic PEM's needed for their usage and still have loading of about 2000 items/s. Using "phantom nodes" only to be filled in later (either on click or on coming into the "visible area" [sounds familiar ?<g>]) for the top node level I was able to give the users a clickable control fast, and as they scrolled along the TV phantom were loaded before the node reached the visible area. Only if opening a node with a large amount of daughter nodes (here I went for "Fill then all to the next level") there sometimes was a small pause, depending on the amount of data in the node and next level sub-nodes. Took some fiddleing... Nowadays I would probably just fill the upper 2
>levels, with level 2 having phantom nodes.
>
>So "control filling speed" was high enough not to be any argument, and the corresponding data structure had to be built in any case (with very similar level of complexitiy). Since the user could decide the granularity of the basic select filter (nothing stopping them to query for * on lastname <g>), there was an estimate on the time needed based on reccount and selectivity and machine speed. If the query would take less than 1s it was executed as such and over that level wait windows of query status and every 500 Items loaded in the TV were shown (with a message box shown before for really ridiculous amounts of data <g>).
>
>regards
>
>thomas