Write Conflict Error message

[abette]

Hi there,
The user is getting a Write Conflict error message when using a Form in Access. He navigates to the last record and clicks to add a new record. This works successfully, however, when he navigates back to the previous record, he receives the Write Conflict message box.
Somethings to note: The form's record source is a table that was pushed to SQL server. I've encountered this message before in another database when trying to update a record that uses a SQL table.
Any suggestions?

Thank you!

 

[theDBguy]

Are you using any code to update the table from your form?

 

[abette]

Are you using any code to update the table from your form?

No. Straight up Access with a Save button that is a macro.

 

[theDBguy]

No. Straight up Access with a Save button that is a macro.

Is the macro using any UPDATE query or RunCode action?

 

[AccessBlaster]

Is the user sharing a frontend?

 

[gemma-the-husky]

Often, the user himself causes this. If you go to a record, and edit the record, then open the same record in another form, you are likely to have the same record dirty in 2 forms, and you give yourself this error - which is the standard "optimistic locking" error.

One solution is to save any record edits before opening the popup form.

If you add record selectors, you will see the pencil indicator to show a dirty record. The new record might be getting dirty by initiallising some fields.

 

[abette]

Is the user sharing a frontend?

No. actually the database is only used by him to track his deliverables.

 

[abette]

Is the macro using any UPDATE query or RunCode action?

No, the save is a straight Macro generated using the command button feature in the Design view window. It automatically generates the macro for you.