Richard,

>If by, "Is the OptionGroup properly bound to the table field", you mean the column's Bound property... it is set to .F. The radio buttons are purely conceptual...the have no direct representation in the database/table/view.

That's your problem then. There aren't several rows of data for the opg to be bound to, and the way VFP does grids the controls are just painted for all but the current row. If you reset Sparse to .T. it might work for you, as long as you don't mind how the non-current records display in the grid.

You can add a column to the view to bind the opg. Or yank the opg out of the grid and just a single one that is "visually associated" with the current record of the grid.

> It's only there to facilate the correct setting of the Closed field, and to enhance readability for the user.
>
>The Column.Name = colProcess
>The Column.Bound = .F.
>The Column.ControlSource = (None)
>The Column.CurrentControl = optProcess
>The Column.Sparse = .F.
>
>The OptionGroup.Name = optProcess
>The OptionGroup.BorderStyle = 0 - None
>The OptionGroup.ButtonCount = 3 (Complete, Active, Canceled)
>The OptionGroup.ControlSource = (None)
>
>The optCompleted.ControlSource = (None)
>The optCompleted Click event does:
>replace vpOrderItems_order_ID.Closed WITH DATETIME()
>ThisForm.Refresh
>
>The optActive.ControlSource = (None)
>The optActive Click event does:
>replace vpOrderItems_order_ID.Closed WITH {}
>ThisForm.Refresh
>
>The optCanceled.ControlSource = (None)
>The optCanceled Click event does:
>replace vpOrderItems_order_ID.Closed WITH {01/01/1900}
>ThisForm.Refresh
>
>(eventually I'll color code the rows: White for Active, Green for closed, red for canceled)
>
>The blanking code affects only the current record.
>
>I am using a parameterized view, vpOrderItems_Order_ID, parameterized on cOrder_ID (indicated by the last half of the view name).