I have an Access Front End/SQL Server 2008 R2 Back End application that has been in production for over a year. Some users recently started reporting some Write Conflict errors. In a View with about 10,000 rows, I have isolated one row that creates the problem. (There may be others, but I haven't found them.). There are about 10 Memo fields in the view. When I open the View in datasheet mode and try to change any of the Memo fields in this one row, I get a Write Conflict error. I can change the same Memo fields in other rows fine. I can also change the same Memo fields in the "bad" row if I open the underlying Table, rather than the View, in datasheet mode. If I open the Table or View in SQL Server Management Studio, I can change the Memo, actually nvarchar(MAX), fields successfully. The table has included a Timestamp field since the outset. We normally have over 75 users in the database at once and have never had this problem before. I ran across a few articles that said that on occasion the "pointers" that Access uses with Memo fields could be corrupted, but I don't know if this applies only to Access Backends, rather than SQL Server Backend. I removed and re-linked the views, but that had no effect. Any suggestions would be appreciated... a solution would be honored with copious amounts of beer... Eddie