Terry,
Back when MM.Net was a mere glimmer in the eye of those lucky enough to behold it, I remember adding this as the New button's Click method:

private void cmdNew_Click(object sender, System.EventArgs e)
{
   mmBusinessObject bizObj = this.GetBizObj(this.grdYourGrid.BindingSource);

   //Move to the new record in the recordset
   this.grdYourGrid.NavigateData(this.BindingContext, bizObj, mmNavigate.Last);
}

Without this, the form wasn't refreshing to display the new record's values. Thought this was going to be incorporated in a framework upgrade at some point.

Lately I've been bogged down with VFP programming here at work and a nesting wife at home, so I haven't had much opportunity to re-test it.

Hope that helps,
---J

>Kevin,
>
>The following code is used to register the primary business object. I also added the oClientBusiness object to the BindingSource property and I still do not have the form refreshed with the added row.
>
> 'Instantiate and Register the client business object
> Me.oClientBusiness = CType(Me.RegisterPrimaryBizObj(New ClientBusiness), ClientBusiness)
>
>
>Save, Cancel, delete and close buttons work as I would expect.
>
>My question stated another way. Is there behavior in the NEW button or methods it calls, to REFRESH the form with the newly added row? After clicking the NEW button I have checked and there is a blank row added to the dataset table ‘CLIENT’ but the previous row( with data ) is still visible on the form. Is there default behavior in the button to refresh the form's bound controls? Do I have to add code to clear bindings and re-bind to the blank row?
>
>Thanks for the help,
>
>
>Terry Carroll