For the similar requirement I thought about using a mover, but hadn't found a decent one and decided to use multiselect grid instead. In addition I added a listbox, which showed selected items. This listbox also had ability to delete item (unselect). Works fine, though I have only ~300 items.

>>Hi Mark.
>>
>>>> I have a listbox with multiselect = .t. I have about 1500 records in it. <<
>>
>>IMHO, even a listbox with a lot less than 1500 items in it is a user-surly UI. Personally, I think your end-users will hate it.
>>
>>>> other idea is to put multiselect grid instead of listbox. but then grid does not have interactivesearch. <<
>>
>>I think this is a much better idea. You do not even have to write your own incremental search grid. If you have a copy of "1001 Things You Wanted to Know ABout VFP" (Akins, Kramek, Schummer - Hentzenwerke, 2000), there is an example of exactly this kind of multi-select grid in chapter 6. You can also download ingrid (an incremental search textbox) from the files section here.
>>
>>It also becomes very quick and easy to find all the items selected in your multiselect grid using SCAN FOR lSelected.
>
>Hi Marcia,
>
>Maybe I'm missing somethimg but I don't see how multiselect grid solves a problem for a user to see at glance what was selected already. It's very easy for him/her to get lost with 1500 records in the grid.