LINQ to SQL concurrency conflict - Looks like a clean attach with proper row versioning?

Try loading the original object in behind the new version else { _db.GetTable(). Attach(c, true); _db. Refresh(RefreshMode.

KeepCurrentValues, c); } I've learned this technique from this article in the section: concurrency patterns for Update (and Delete) operations.

Try loading the original object in behind the new version. Else { _db.GetTable(). Attach(c, true); _db.

Refresh(RefreshMode. KeepCurrentValues, c); } I've learned this technique from this article, in the section: concurrency patterns for Update (and Delete) operations.

Thanks a million. That illuminated something I was missing about reattaching an object to the DataContext: the properties of the attached object that weren't explicitly set for the save operation are empty, which the update tries to save over the currently saved values... Doh! Not what I wanted.

– I Have the Hat Oct 22 '08 at 18:01.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.