Greetings Kevin,

For editing single instance controls (Patient name, address, etc.) I have a Patient Biz obj registered on the page with the entity loaded via sproc. When edits are saved I set the entity values to the control values and then SaveEntity().

There are several one-to-many related tables that I want to allow the user to CRUD through GridViews

For adding new records I've added controls to the footer record of the GridView and to the EmptyData template (when there are no records yet for the GridView for the Patient). With these I'm just checking in RowCommand event handler for the command name and creating a new entity and saving it - no problems there.

Deleting from the GridView via ODS is working fine.

I'm trying to allow editing within a GridView with the ODS. Basically, the same functionality shown in the jump start GridView editing samples but with an ODS doing the heavy lifting instead of programmatically manipulating DataSets. When we had talked at the San Diego Code Camp you had said ODS was preferred.

Since SaveEntity and SaveEntityList were just wrapper methods around SaveDataSet I specified SaveDataSet as my updated method on the ODS

Right now the GridView is trying to hit an update method with parameters it is generating based on the columns in the GridView. What I was trying to find out from you was if there was a default update method one could specify for updating or if I will have to create a method for each Biz obj that maps to columns use in any GridView that use that biz obj. If that's the case fine, but with no documentation on using the ODS I didn't want to create all these methods and then find out later there was an easier way.

>
>Sorry you've been wrangling with this for so long--I thought you had a solution a while back. At any rate, can you describe to me how you have set up your form for editing and saving changes (including what are the user gestures) so I can give you the best answer?
>
>Best Regards,