Hi Nadya,

I apprecaite that. Please e-mail that to me to doron@dfarber.com and I can test it on my project.

Thanks,

Doron

>Hi Doron,
>
>I can probably can send you my implementation, if you'd like. However, I'm not sure, if this is what are you after...
>
>I implemented is as MultiSelect grid + listbox only to show, what is selected. The items in the multiselect grid don't disappear, they just stay selected...
>
>>Hi Nadya,
>>
>>I was thinking to use a mover obejct with grids it will have much more flexiblity. How did u resolve the nover class. Since I also need a mover that when ever I move an item from left to right the item on the left chabges its color so the user can select it more then once.
>>
>>Regards,
>>
>>Doron
>>
>>>>Nadya,
>>>>
>>>>I don't think I misunderstood *s*
>>>>
>>>>When you change parent records you Requery the child views right? If the user makes changes with the moverlist you can either TableUpdate() to commit them or TableRevert() to cancel. In cases like this I typically use parent table navigation to do implicit saves to child views, they have an undo feature to cancel changes so I let them work as unfettered as possible without inane Do You Want To Save Changes dialogs popping up all the time.
>>>
>>>How do you update child table? How do you delete records from the child, if you delete record from the parent? Do you use RI? I'm working in this direction right now.
>>>
>>>BTW, instead of Mover I implemented MultiSelect Grid + ListBox. When I select items in the grid, I show selections in the Listbox (Multiselect=.t.). I also allow to delete records from ListBox, and this updates selections. Everything works fine so far, except for delete (I haven't created a RI yet).
>>>
>>>Thanks again for your help.