Hi David

>This basically goes against O-O theory. Rather than having two different classes that define the same properties/methods, You should promote the common items up to a parent class that the two classes are derived from. You your case it sounds like you may need to create a new class and insert it into your inheritance tree and then redefine your two classes from this new class.

Actually I was trying to switch autocomplete cbo's. I wanted to discontinue using one kind of cbo (already used in apps under the name acboautocomplete subclassed from the original autocomplete cbo). And put in a new autocomplete cbo so the subclass remains the same, acboautocomplete.

So there was no way common stuff was going up to the parent class.