Hi Bonnie

Yes. UserControl was the term to use not Component. However, the question still remains that if I do create a UserControl, will I be able to add/override functionality when I use it?

For instance the combo box(in the image) now displays a choice of 4 items - AMEX,VISA,BCARD,OTHER

Suppose I later want to add a single item to the contents of the combo(making it 5 items) for a single instance of the UserControl, will I be able to? And will I be able to add a method to it as well?

>Hi Bernard,
>
>You'd want to use a UserControl for this rather than a Panel (you can stick the Panel on the UserControl if you want to). The UserControl *can* be visually designed.
>
>~~Bonnie
>
>
>
>>Hi Viv
>>
>>New link. Sorry for the WPF link. Please treat this as a winform Q.
>>
>>http://www.foxite.com/uploads/9435e32d-633b-4007-8084-c8be972e0d36.jpg
>>
>>Basically I would be creating a new "component" rather than a class?
>>
>>Q is that with a component so designed and added to the toolbar, will it have the same capability as a class?
>>Can I override its methods and properties/fields and even add my own as I could with a class?
>>
>>Are there any disadvantages (something I cannot do ) with a component over a class?
>>
>>Thanks
>>
>>Bernard
>>
>>>
>>>The link you posted appears to be broken but it seems you are asking about two different things.
>>>As far as sub-classing the base controls goes - yes you have to do it in code - but there are a limited number of properties that would typically need to be defined. If it's any consolation you can't do it visually in WPF either :-} - but it *is* easier to do it in code......
>>>
>>>In the second case (the ability to add components to the Toolbox for re-use) then you can build a UserControl.
>>>
>>>>Will Visual Studio ever fulfil its name and allow a class to be designed visually?
>>>
>>>Probably not.