>
>Now I know what has happened: I have an optiongroup on the formclass. I changed the buttoncount of this optiongroup (added one option) and made the optiongroup larger in order to show all buttons.
>Moreover, I moved the added button (Option8) to the position of Option2, and moved all other buttons down so the options' order was:
>Option1
>Option8
>Option2
>Option3
>etc..
>
>In the form, the Option8 was added, but the optionbuttons were not moved down, so I did not see the Option8, it was still hidden behind Option2.
>I could reproduce this problem. Interesting behavior... :-)

Not really a problem. There is no way the parent class could know about the option 8 you put in the form instantiated from it. So the instantiated form put the new button exactly where it was in the parent class.

In short VFP did what always drives me crazy in a programming language. It did exactly what you told it to, instead of reading you mind and doing what you wanted it to.

In general (and this applies to any object oriented, or even object based language) placement of controls generally does not cascade down well to child classes -- and almost always requires tweaking at the child class level.

There are some controls in the file section of this thread that will autojust forms, and space out controls for you. You pay for this by giving up a lot of control over the appearence of the form..