What's your problem with the "combined" listboxes of the mover class? It's two listboxes in there, too. You need to modify code used to fill one of them with your search result, but isn't that possible?
Regardless of using that FFC class or not, it depends very much about how you populate the one listbox, using a cursor controlsource needs much different code to delete an item than a listbox filled by Additem().
I developed my own mover class and it has some properties on the container level to specify source and destination aliases. So it's based on cursors as rowsources. Moving items then is deleting them from one cursor and adding them to the other. That doesn't even need addressing the controls themselves. It's a bit tricky, using a cursor with a primary index I make use of both DELETE, SCATTER, GATHER and also RECALL, eg when moving a record forth and back again, the record needs to be RECALLed in the source cursor, because the primary index wouldn't allow adding it once more.
Bye, Olaf.