>Well, for the mover functionality it is easier to manipulate the arrays than cursors - that's why (IMHO) most of them are array-based. In my mover class that you tried, I had save and restore selection functionality before, then I dropped it because it overcomplicates the class (probably unnecessary in most cases) and users' understanding on how it should work is different.

Nick,

If you have class, which has:
1) Auto-resizing (simple enough)
2) Drag+drop in addition to buttons
3) Multiselect
4) Ability to show several (say, three) columns
5) Save+Restore ability

and you can share this class with me, I would really really appreciate it.

Otherwise I have to proceed with Multiselect grid approach, which is not bad too.

Right now I found another hole in our framework, which I have to somehow overcome. As always, I didn't receive the appropriate response from the person, who is in charge of our classes, so I have to struggle with it in this particular instance.