According to Chris Sells's book "Windows Forms 2.0 programming" you can't change the configurations of inherited tool strip controls, layout-panel controls, and DataGridView because they are all locked. So it is by design.

Just curious , does similar limitation apply to usercontrol used as a container. Unlike Visual Foxpro when placed on a form, children are not editable via property sheet regardless of access modifier. No problem to deal with them programmatically.



>Dan,
>
>This is the first I've heard of this new TableLayoutPanel. Anyway, it seems to be either a bug or a limitation of the TableLayoutPanel itself. Not only are all the controls that are placed on the panel unavailable to be changed from the Property Sheet, but so is the panel itself. I thought that maybe if the Panel was made public/protected, then the controls contained on it would be accessible, but even that didn't work. I really think it's a bug.
>
>~~Bonnie
>
>
>>I just created a new Win Form; inheriting from Form. Then changed it to inherit from my base form. I'm getting the same behavior.
>>
>>I can change properties progmatically; at least it will build the project.
>>
>>>Dan,
>>>
>>>>I have a form with a table layout panel, a couple of lables, textboxes and a button. All the controls are "PROTECTED".
>>>>
>>>>I'm adding an inherited form to my project that inherits from the above form. In the new form, I cannot change any properties on the existing controls. I've done this multiple times with other inherited forms, but for some reason, cannot on this form. Even if I go to the base form and mark everything as "PUBLIC", I cannot modify any of the existing controls.
>>>
>>>Hmmm...that should definitely work! I take it you've tried to create a new subclassed form from scratch. When you set the base class form properties to public does it still show the "protected" or "private" icons next to the controls in the subclassed form? Does it let you change them programmatically?
>>>
>>>Best Regards,