> that seems like a lot of work to do for each KMover... especially for one that works good practically As-Is. But is this the only solution to not break the Business Rules?

Dustin,
KMover isn't your average control... in fact it's a collection of controls and objects so you got to expect some extra massaging when you need it to be smarter than the average control. I've used it twice and both times had to adapt tit to my needs, so I think what your seeing is par for the course.

There is another trick as far as replacing one of the listbox driver bizobj with your own bizobj that will alleviate much of the copy/paste ho-hum activity. Dig into the Cmover classlib (i think).... whereever Kevin has all the subclassing stuff for this control together & find the class definition for bizobj you wont to adapt. Now you can either subclass your own bizobj from that class, OR Jump out to the command window and do a CREATE FORM. Copy/Paste the bizobj stuff from class designer to form designer and then do a SAVE AS CLASS from the file menu. Presto... you got a duplicate of the original class definition that you can adapt to your hearts content with only one copy/paste action. And if your app has a general base bizobj class for common app-specific functionality, you can use class browser to redefine the copy/pasted bizobj to your base bizobj class and now you got everything together in the same class!