>>>>Nadya,
>>>>
>>>>When ever I give the users a selection grid I simply include a boolean field and allow the user to check on/off the items they want to select. I really don't like multipick listboxes because the are "user fragile" one little misclick and they've potentially lost all of the rest of the work they've done picking items elsewhere in the list. Using a checkbox in a grid avoids this.
>>>
>>>Hi David,
>>>
>>> I gave some thoughts into this interface problem, I also discussed it here and with my colleague, and the mover type interface seems to be the best from the user's perspective.
>>>
>>> For this particular application I'm working right now, I need to have an ability to "save and restore" selection. In other words, when user navigate from record to record on the parent table, List with selected items should display towns, which were selected for this region.
>>>
>>> So, the ideal mover, which I have in mind, should work with any type of Record Source (array, cursors, values, doesn't matter), should allow to work with multiple columns (AFAIK, these mover classes work with only one dimension) and allow to pre-populate the second list based on entries in the table. It also should have resize capability and drag and drop. Ideally it would allow to sort by clicking on the header (yes, I'm talking in terms of Cetin's multiselect grid) and have a re-order buttons on the left.
>>>
>>> _FFC _Mover class seems to be over-complicated, too deep in class hierarchy, doesn't have enough comments, etc.
>>>
>>> Our own class is very primitive and I believe, is only oriented on values as a RowSource.
>>>
>>> So I'm seeking for something flexible and quite simple for my particular needs.
>>
>>So, why don't you write one? :)
>
>Well,
>
>1) Don't have much spare time.
>
>2) Cetin Basoz has already a class of my dream, but I'm not sure, how to present the idea of purchasing this class to my manager.
>
>3) He suggested to use Multiselect grid class, which I already implemented in another application. I'm not 100% sure it's the best class here because of the problem mentioned by David at the top of the this message, but I guess, this is my best shot for now.

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.