Write Conflict. Record Changed By Another User


WRITE CONFLICT: This record has been changed by another user since you started editing it…

Oh really.  But there is nobody else in the record!

This can happen if you have Bit fields with NULL values set to default to 0 and NOT allow NULL (you designed the table wrong the first time and changed it retroactively).  When you edit the records in Access it changes the Null to a Zero by itself, and then you change the value to what you want….and it gets confused thinking there are multiple updates happening.  The trick is to add a Timestamp column to the SQL table and make sure you have a primary key.  Problem solved!

Did this work for you?  send me an email and let me know!

Related Posts

Access 2016 Relationships

Short blog today, this is a great read on relationships in Access 2016: Access 2016 Relationships Thanks to Microsoft for this one!

Microsoft Access Union Query from Hell. Skill Level: Demi-God

The worst query I ever had to write which powers a master report for the database user.  Here it is.  I don't think I can make it smaller, there were too many weird rules, aggregates, and translations in it.  And we needed to pull different columns based on criteria. ...