Mike,

So what's relevant and reuseable should go into the class, then your two cbos should be subclasses of the newly created class. Think of this as a chance to refactor/refine your class design.

Let's call cboX your existing class you want to copy to cboY in this operation and assume it's based on a root level subclass of the VFP classes so there is this current hierarchy:

ComboBox
   cboBase && isolates you from VFP baseclass changes and you fix what's wrong with the VFP baseclass here
      cboX && some reuseable good code exists here now

You should consider doing this

ComboBox
   cboBase && move anything  from cboX to here that is useful in EVERY cbo you will ever use
      cboLevel1 && bad name... but move any cboX stuff that is useful to this subset of cbos here
         cboX && changed to derive from cboLevel1 the only code that remains here is specific to this instance of the class
         cboY && new instance of the class you are wanting to start this copy operation

>I understand what you are saying and perhaps I have a bad class design, but, I really do want to copy the class as a starting point. I'm going to remove a lot of the existing properties and methods and add to it. Rather than trying to retype all that stuff, I figured it would be easier to copy it, delete the unnecessary parts, then go from there.