This is similar but not at all identical to this post about LINQ to SQL because it's using a different framework and that has different capabilities. Someone mailed and asked how we can detect concurrency problems with Entity Framework in order to ensure that when we submit changes to the DB we first; Present the user with a list of all the concurrency errors in one go Present the user with their changes versus the DB's current data Ask the user how to go about resolving each issue Repeat until all the changes get to the DB one way or another I can use the same tables and scripts and so on that I used in the previous post about LINQ to SQL. So...if I've got this table in my DB; create table Person ( id int identity primary key , firstName nvarchar(30), lastName nvarchar(30), timestamp ) with data; insert person(firstname,lastname) values ( 'first1' , 'last1' ) insert person(firstname,lastname) values ( 'first2' , 'last2' ) insert person(firstname,lastname) values ( 'first3' , 'last3' ) and I bring this into an...