I am using the generic dynamic SQL data access layer provided by MM .NET version 2.4. I put a breakpoint in the code and traced the creation and execution of the update and delete commands created by the CommandBuilder. I was surprised that the update command included updates for every column whether modified or not. The Developers Guide says that dynamically generated update commands only send columns that have been changed as part of the SQL update command.

Also I use a timestamp column that I expected would simplify testing for concurrency conflicts, but both the update and delete commands that are dynamically created at run-time seem to compare every column to its original value to determine if there is a concurrency conflict.

Am I misunderstanding the Developers Guide or am I doing something wrong? What I am seeing does not seem to be very efficient and seems to disagree with the Developers Guide.

Sam Tenney