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

[David Emerson]

That might be a pain for the users as the forms are continuous and the users
are updating multiple rows at a time. 

At this stage we have got around it by removing the timestamp field which
has solved the problem.  I just need to confirm that this won't cause other
problems.

David

-----Original Message-----
From: dba-SQLServer [mailto:dba-sqlserver-bounces at databaseadvisors.com] On
Behalf Of Arthur Fuller
Sent: Thursday, 18 October 2018 11:12 p.m.
To: Discussion concerning MS SQL Server
Subject: Re: [dba-SQLServer] Write Conflict Error - Access and SQL

In that case, I'd do a form.Refresh the row is initially saved. You can
either call the Refresh explicitly or re-enter the RecordSource (as text).

A.

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

> Hi Arthur,
>
> The problem is that there is only one user in the database.  They get the
> error when they change a record, move to another record (which saves the
> first record change),  go back to the first record and try to change the
> same record again without refreshing the data.