>Addendum- MS is indeed planning a fix... see http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1179601&SiteID=1 ... the response from MS is at the end of Page 1 plus several useful responses on Page 2.
>
>I'd be very interested to hear how others are managing change tracking and concurrency in a multi tiered NET scenario. If they';re simply returning datasets back to a SP for handling, what happens if 2 users are making changes at once? E.g. one user changes customer address while the other user changes phone number. The first user updates. When the second user updates, how do you prevent overwriting of the newly updated address with the old value? If you're going to pass around objects or entities, surely they need to carry with them change tracking information, or be limited to values that have actually changed. Intriguing. Hopefully somebody can enlighten me.

What I usually do is timestamp the record. If the timestamp doesn't match when I update the record, then I return an error message saying the record has already been updated. I suppose I could return the update record and show what differences there are between the two records, but I have never had to go that far before.