That sounds about right, Kevin (although I haven't looked at that Mover class at all, so I don't know what it's like).

~~Bonnie


>In VFP, I had a container class that served as a 'mover' function.
>
>Basically, it was a container class with two list boxes (source/target), and some command buttons for MOVE ONE, MOVE ALL, etc. (Basically, it was the MOVER stuff from Griver's Codebook. I made a custom container out of it, changed a few things, and then dropped it on a form when I needed it).
>
>I want to do the same thing in C#. I pulled down the MOVER.NET from the UT Forum. It seems to me that to do the same in VFP, I'd want to do the following...
>
>1) Create a new project in C#, as a Windows Control Library.
>
>2) Drop the list boxes and command buttons from the mover form that's in MOVER.NET onto the empty UserControl in the new Control Library Project.
>
>3) Build the project, and then add it to the toolbar.
>
>4) Drop the usercontrol onto any form where I need it.
>
>(Yes, there's a MOVERMANAGER.CS with most of the logic...I realize that's separate from the general UI piece).
>
>Generally speaking, is this the best way to carry forward this approach from VFP (created 'composite' container classes and then dropping them onto forms as needed), or is there a different/preferred way?
>
>Thanks,
>Kevin