Write Conflict with SQL Server

[Learn2010]

I posted this on 6/12/2014, and got no resolution.

START OF POST
I have read several posts concerning Write Conflict errors. I have tried several options and am still getting the error message. I am using SQL Server as the back-end. Are there any special considerations I should know of to prevent the Write Conflict errors because of the SQL Server?
END OF POST

The Write Conflict error doesn't happen when using Access as a backend. Apparently, this is a SQL issue. Should I post this on a SQL forum or does someone on this site understand the issue and can offer a solution?

Thank you.

 

[Learn2010]

This got rid of the Write Conflict error.

Private Sub Form_Error(DataErr As Integer, Response As Integer)
If DataErr = 7787 Then
Response = acDataErrAdded
End If
End Sub

I am still getting the message that you can't save the record at this time when I close the database with DoCmd.Quit, or Application.Quit acQuitSaveYes, or Application.Quit acQuitSaveNo. This happens after I return to my Main Screen (my dashboard), and the save or update process has been completed.

Does anyone have a solution?

 

[JHB]

Are you able to add a record to the table/query directly, (without using a form)?
You mention you've tried several options, but what exactly did you try?

 

[DavidAtWork]

go to your backend database in SQLserver and try adding a new field to the table, make it a timestamp datatype. Do not try to use this field in your Access front end, but should prevent the write conflict you are experiencing.

David