On our database we are currently replicating some of our tables using triggers, it seems that whenever a CRUD operation is called, on one of the replicated tables the "cmd.ExecuteNonQuery() in DbDataStore.ExecuteNonQuery" returns rowsaffected = 2, one for the actual update, and one for the trigger update. (by the way i didn't setup the replication, I just bound to use it that way) The result is obviosly that the optimistic locking fails, since it always test for rowsaffected=1, so... The wish from my perspective would be that we somhow could specify expected rowcount on table level, Don't know if this is to far out (or is already solved, somhow, u'r version = 1.3.2), but i have to try, since it's possible that I'm not the only one facing this problem. Br Casper