Rich,

You can't "call" events. Click() is an event. It means that a MouseDown() event occurred and then a MouseUp() event occurred on the control. It's this sequence internally that causes VFP to fire the Click() event. When you call the Click() method the only thing you'll ever accomplish is to run the code that you put in the method in the class hierarchy. Setting the .Value in some method will cause the ProgrammaticChange() event to occur.

Honestly I can't come up with a good use for the .Value of a CommandGroup anyway. I also don't have a whole lot of use for CommandGroups anyway because subclassing the buttons used in there is a hassle. Individual CommandButtons in general are better.

>I have a command group of four buttons. When I click any button with the mouse the value property of the command group is set to the value of the button number (there’s no code in the event). However if I call the click event of the button programmatically the value property never changes. Using the event tracking feature of the debugger hasn’t shed any light. What event is responsible for changing the value of the command group?