Sam,

>I did look closer and every column is being updated even if the column was not modified. Why should it work that way?

Jeff is right on the money...I answered this one via private e-mail, but I'll post my response for everyone to see. If you step through the data access code, it appears that ADO.NET is going to send all of the column values to the back end regardless of whether or not they have changed. However, if you run SQL Server Profiler, you will see only the columns that have changed are actually included in the update statement.

>Where can I find the ConcurrencySelectStatement that you mentioned?

It's located on your business object.

Best Regards,