Terry,

Ok, you can do what you want to do. By setting, a property you can modify the control inside of the design view in the property tabs, and that is no problem. If you really want full control, simply make the Control PUBLIC in the base class.

Then you can manipulate it in any inhertied controls, I think your problem is. By default VS.NET makes a control protected or private, and if you simply change it to public you will be able to do what you want with it.

Morgan


>Bonnie,
>
>Thanking you for your tip.
>
>I gather from your answer that once a form is sub-classed from a form containing controls, ALL the control properties that would normally be editable in the control's property page must be set in code.
>
>This would seem be preclude creating composite form classes with controls on the form since it would just defeat the purpose of RAD development by requiring properties like location, size, backcolor etc to be set in code. I'm not sure of the reasoning why .NET would not alow the property page of controls to be used in inherited forms, with maybe the exception of the Name property.
>
>Oh well, clients want .NET they will gladly pay.
>
>
>Thanks again
>
>
>Terry Carroll