>Nadya,
>
>> 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 set the buffering to table, and just use a TableUpdate() to save and a TableRevert() to restore.

David,

You seem to misundersood my original problem. I meant, when I navigate from record to record in the parent table, mover class, which is based on lookup Towns table, should show selected towns in the list of selected items. The selected towns are stored in RegionTowns table (I use TownsInfo view).

Buffering is set to 5 and I use three views: CustomerInfo, RegionsInfo, TownsInfo.

Anyway, I abandoned mover idea, and almost finished programming of multiselect grid idea.

>
>> 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.
>
>You could simplify things if you coded to just work with cursors and maybe provide methods on your mover container that would take the other kinds of sources and convert them to/from the cursors it uses.

Yes, I was thinking along these lines. When I finish this project and another one, which was just assigned to me, I would make more research in this direction.

Thanks for your help.