I think you have a correct understanding of what I want to do. Edits would be saved only in the Dataset until the user chose to Save the entire Dataset/Business Object or they tried to close the form at which time it would ask if they wanted to save the changes. If something happens and the changes are not successfully saved to the backend database, then all the changes are lost and the user will have to try again. Under normal circumstances the user would be clicking the Save button quite frequently as they edit only a handful of records at a time. This seems to be a very basic need especially when editing child business objects such as line items on an invoice. The entire invoice should be saved to the backend database only when it is complete. Any help you or Kevin could provide would be appreciated.

Sam

>I haven't tried to do that but my take is it wouldn't be hard to do. If you edit the data in textboxes then you still need to navigate to the next record and save the edits back to the Dataset even if not saved to the SQL back end. There would be a point where the data needs to be persisted to the SQL. Do you do this on closing the form? What happens if the form doesn't get closed properly or something?
>
>If you want to do something like that, I can probably take a look at what I thought would be involved.
>Tim
>
>>Thanks Tim,
>>
>>I understand that anything I can do in Dot Net, I can do with the Framework, but I was hoping the Framework would provide a built in way to provide this functionality without having to modify the basic design of the framework.
>>
>>To answer some of your questions, my data backend is SQL Server. I would like to use grids and/or navigationtoostrips but only for selection and navigation purposes not for editing. The editing would be done in standard textboxes etc. It seems that the basic navigation logic in the Framework prohibits me from navigating without first saving changes etc.
>>
>>It seems to me to be a lot of work to work around the navigation logic built into the Framework. Any ideas?
>>
>>Sam
>>