[dba-SQLServer] Write Conflict Error - Access and SQL

[Arthur Fuller]

I didn't follow Susan's link, nor can I provide precise instructions, but
my feeling is that this is the responsibility of the database, not the UI
or UX. Upon receipt and acceptance of a row-lock. the first user who
succeeds in locking a row has control until the update has completed or
cancelled. Other users attempting to edit the row of interest should
receive a message that someone else has locked the row; please try again in
a minute or so.

Arthur

On Wed, Oct 17, 2018 at 2:43 PM David Emerson <newsgrps at dalyn.co.nz> wrote:

> Thanks Susan,
>
> I will try removing the timestamp to see if this helps.  Since records are
> almost always only used by one user I may get away with it (famous last
> words).
>
> Regards
>
> David Emerson
> Dalyn Software Ltd
> Wellington, New Zealand
>
>
>
> -----Original Message-----
> From: dba-SQLServer [mailto:dba-sqlserver-bounces at databaseadvisors.com] On
> Behalf Of Susan Harkins
> Sent: Thursday, 18 October 2018 1:30 a.m.
> To: 'Discussion concerning MS SQL Server'
> Subject: Re: [dba-SQLServer] Write Conflict Error - Access and SQL
>
> I've read about his problem before, but I don't actually have a solution or
> hint for you, but perhaps this will help:
>
> <
>
> https://social.msdn.microsoft.com/Forums/sqlserver/en-US/ce92437b-da89-47d9-
>
> 9bbf-38a84b74ee62/receiving-write-conflict-error-when-trying-to-update-linke
> d-sql-server-table-that-contains-a?forum=accessdev
> <https://social.msdn.microsoft.com/Forums/sqlserver/en-US/ce92437b-da89-47d9-9bbf-38a84b74ee62/receiving-write-conflict-error-when-trying-to-update-linked-sql-server-table-that-contains-a?forum=accessdev>>
>
>
> Susan H.
>
> Hi Listers,
>
> I have a client with an SQL database in SQL 2014 with an Access accde front
> end running in Access 2016.
>
> A form uses an ADODB.Recordset assigned to the forms Recordset property to
> get the records for the form.
>
> The user can change a record and save it ok the first time but if they try
> to change the same record again without refreshing the data they get a
> Write
> Conflict error "This record has been changed by another user since you
> started editing it. If you save the record you will overwrite the changes
> the other user made.
>
> Copying the changes to the clipboard will let you look at the values the
> other user entered, and then paste your changes back in if you decide to
> make changes."
>
> The table for the records contains a timestamp data type field, and doesn't
> have any bit fields (these are the two main suggestions from other posts I
> have found).
>
> I have used the same Access database in Access 2010 with SQL2008 and it
> doesn't cause the error.
>
> Where should I start looking to work out why the form works on one
> configuration but not the other?
>
> Regards
>
> David Emerson
> Dalyn Software Ltd
> Wellington, New Zealand
>
>
> _______________________________________________
> dba-SQLServer mailing list
> dba-SQLServer at databaseadvisors.com
> http://databaseadvisors.com/mailman/listinfo/dba-sqlserver
> http://www.databaseadvisors.com
>
>

-- 
Arthur