Frank,

The code for saving is no different for adding a record vs. editing a record. But here it is:

 protected void btnSave_Click(object sender, EventArgs e)
    {
       
        DataSet dsClient = (DataSet)Session["dsClient"];
        if (this.Save(this.oClient, dsClient, this.oClient.TableName) == mmSaveDataResult.RulesPassed)
            mmMessageDisplay.DisplayMessage("System Confirmation", "Record Successfully Saved",
                "ClientsForm.aspx", 3);
    }

Note that I send the form back to the list form after successfully saving the record. If there were errors the edit form would remain with the error icons displayed.

As far as unbound combos/dropdownlists, I am not sure what you mean. If these controls exist and they are not bound, what is their purpose? If they are bound to the business object then they will be part of the save process.

>Hi Bob,
>
>that's pretty much exactly what I have. Can I see the code for saving? Also how do you handle unbound combos/dropdownlists?
>