>>>>Jay,
>>>>
>>>>The OOP concept here is that if you don't need what is in the class then the object is not a member of that class, it is a member of some other class.
>>>>
>>>>IOW, the item you are wanting to remove probably should not be defined in the class defintion that you are using (because you are using the class and don't want the item).
>>>
>>>Ok, that makes sense. How to handle a situation where you have buttons in the class like Export to Excel, Export to Text, Export to Word, etc., but you find that for the form you are working on, there is never a need for the Export to Word button, but you need all the others and like how they behave?
>>
>>Hide the button or remove it using RemoveObject method.
>
>Isn't that breaking the OOP concept that Jim is talking about?

You could also use a factory object to add the button as required. Basically be a magician and have the form construct itself as required.

Then you keep your classes less complex at design time and let them become complex at run time.