If your application never sends those changes back to the data source, then you are finished with the update.
If you do send the changes back to the database, then a second step is required.
This serves two purposes: In Windows Forms, the data binding architecture that's built into the datagrid suspends constraint checking until focus moves out of a row, and you do not have to explicitly call the Begin Edit, End Edit, or Cancel Edit methods.
Constraints are automatically disabled when the Merge method is invoked on a dataset.
The following table details the possible values of the Data Row State enumeration: The row has been created but is not part of any Data Row Collection.
After you complete an update, you can re-enable constraint checking, which also re-enables update events and raises them.
For more information about suspending events, see Turn off constraints while filling a dataset.
Information about the changes in a dataset is maintained in two ways: by flagging rows that indicate that they have changed (Row State), and by keeping multiple copies of a record (Data Row Version).
By using this information, processes can determine what has changed in the dataset and can send appropriate updates to the data source.Because datasets maintain multiple versions of records, it's important to keep in mind that more than one version of the records is being merged.