Hi Dragan,
>There's a way around it, but it's in code. With any container class which accepts members of only one base class (grid, pageframe, optiongrup, commandgroup - are there any others?), you can start with ...count=0, and then add objects of that base class as you like, programmatically, in the container's .init():
>
>

this.newobject("opBlue", "myOpButton", "myCtls.vcx")
>with this.opBlue
>...
>endwith

Thats mainly what I do - with grids, the only place I need it. But this is not realy the use of MEMEBER*.

>The trouble with this approach is that you don't see these objects in design time, and their positioning is something you need to calculate. Which is a non-issue for grids and pageframes - the positioning is automatic, you only need to care of their order of appearance - and isn't too hard for optiongroups either. If it's vertical, you just set .left=0 and .top=(nIndex-1)*(.height+2), where nIndex is the button's ordinal number. If horizontal, .top=0 and you need to accumulate the widths.

For the grids I've a method that receive a Array and build up the columns from it. This runs with all the column properties I need. This is from the days where HIGHLIGHTSTYLE was unknown and the "highlighted" row was done with DYNAMIC*COLOR.

>I generally stay away from commandgroups :)

I remeber the existence of such a class. Never figured out what it is good for.

Agnes