All you have to do is set the buttoncount property in the init.

>Hi James
>
>Hmm, the max no. needed. A little ugly but not hideous. I suppose I never thought that way as I assumed VFP would tell me off if I tried to delete a member from a class. But of course, you don't need to - just make 'em invisible or whatever, in .Init(), an resize the opg so that they don't matter.
>
>Anyway, too late now as my class has been around for years, and, to tell you the truth, I haven't been inconvenienced by using std. opbs :-)
>
>Thanks for the idea
>
>Terry
>
>>Hi Terry,
>>
>>Option 1:
>>Set up your class with the max number you would use. In the init of the class you can set the number you need. You won't loose your code if you take away OptionButtons. Ugly, yes but it does work.
>>
>>Option 2: Upgrade <g>.
>>
>>
>>>>Hi Bhavbhuti,
>>>>
>>>>Try MemberClass and MemberClassLibrary properties
>>>>
>>>>Agnes
>>>>
>>>>>Hi all
>>>>>
>>>>>I have put in a VFP OptionGroup on the form. When I increased the button count it used the default VFP OptionButtons, instead I wanted to use my sub-classed OptionButtons. How can I go about this.
>>>>>
>>>>>Please advise.
>>>>>
>>>>>UPDATE: It also seems I can't put my OptionButton inside this container, I cannot paste or drag-drop form the project manager into the VFP OptionGroup
>>>
>>>Just interested, Agnes. I gave up on trying to do what Bhav is some years ago, and made my opg class contain standard opbs. Do you know how you'd do this in VFP7?
>>>
>>>Terry