>Thanks Dave -
If I had done it before it might not be hard, but right now everything is still, er..a challenge:). Can I ask for some hints on your suggestion (i.e. can I look at your 'class' notes)? On a related matter, you did get me to thinking about the fact that the properties reference other buttons that aren't part of the class, and I realized when building a class, that's probably not a good idea, and really does break the concept of encapsulation.

Sylvia,
>
>So make your container smarter. Parameterize it to include an Orientation property, or have the container Init sense if it's been dragged to a vertical shape and just reposition the buttons accordingly. That's not very hard to do at all.
>
>You can always drop the container on the form, resize it and reposition the buttons at design time too. But I wouldn't subclass it just for the layout issue.
>
>>Thanks, I was considering doing that, and that probably is the way to go here. But doing that means I lose some flexibility in button placement and size (for example, the buttons in question for this app are vertically aligned). So then I have to create one set vertical and one set horizontal! That's when I started thinking about this whole issue and thinking "Geez, how far do I want to go with the classes?"