http://www.accessforums.net/ Discussion on Microsoft SQL Server. en Wed, 19 Jun 2013 23:08:32 GMT vBulletin 60 http://www.accessforums.net/images/misc/rss.png http://www.accessforums.net/ http://www.accessforums.net/sql-server/do-you-need-access-record-locks-if-35491.html Fri, 07 Jun 2013 18:57:54 GMT If all my data resides in linked, SQL Server tables (2008 R2), do I need for Access to try to maintain the record locks? If not, how can I disable... If all my data resides in linked, SQL Server tables (2008 R2), do I need for Access to try to maintain the record locks? If not, how can I disable record locks within the database? I have about 200 users using the database and I can't rely on them changing their individual environments. In fact, they use other Access databases that may need to use Access record locks. Thanks, Eddie ]]> SQL Server EddieN1 http://www.accessforums.net/sql-server/do-you-need-access-record-locks-if-35491.html http://www.accessforums.net/sql-server/write-conflict-all-memo-fields-sql-view-35466.html Fri, 07 Jun 2013 02:26:21 GMT 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... 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 ]]> SQL Server EddieN1 http://www.accessforums.net/sql-server/write-conflict-all-memo-fields-sql-view-35466.html http://www.accessforums.net/sql-server/data-has-been-changed-error-35452.html Thu, 06 Jun 2013 15:53:24 GMT I have a SQL database with an Access front end that keeps giving me an error "The data has been changed... another user has edited the record..."

I'm the only user on it, and I'm trying to edit it directly from the table. I already checked my indexes and changed all the bits to ints (that caused a problem a different time), and I'm stuck.

Does anyone have any advice? ]]> SQL Server sdbsadmin http://www.accessforums.net/sql-server/data-has-been-changed-error-35452.html