Rich,

OptionGroups are totally different. opg controls are intuitively bound to a data value. It is designed to display the currently selected value. If you want to change the value of an opg in code you simply set opg.Value = lnTheNewValue. When you do this the ProgrammaticChange() event will fire. If the user changes it via one of the ways available in the UI The InteractiveChange() event will fire.

You never did explain why you want to use the .Value of a CommandGroup. It might be possible to accomplish what you are trying to do without the code you list below.

>Thanks for the response. You're right. Command Groups are problematic. So are Option Groups for the same exact reasons. I was able to solve the problem by simply adding the following code to the CLICK event of each button:
>
>WITH THIS
> .VALUE = n && Where 'n' is the button number
> .PARENT.CLICK()
>ENDWITH
>
>Too bad the control can't be manipulated as desired without this code.