If you look closer, you will probably see that only the columns that change are updated, but the WHOLE table is used to verify there have been no changes to the record since you retrieved it.

By the way, this can cause some wonderful problems if you have computed columns - create the row, save it, edit it and save it again - concurrency error because the computed column in the dataset was not updated, but the computed column in the database was.

You can use the ConcurrencySelectStatement or the dataset's UpdateCommand to change the fields used for concurrency testing. It's an ADO.net issue.

Jeff