I have an Access client on a SQL database (SQL 2017). On some tables there are audittriggers that update auditfields (UpdatedOn, Updatedby).
When I change a record in MS Access, specifically in tableview or multiline forms, go to another record and then back to the changed record, trying to edit the record gives a warning that the record had been changed by another user.
Obviously it's SQL server updating the record after MS Access sends the update which triggers the audit. It's no problem if the record is refreshed in any way before trying to edit it the 2nd time.
I have not build this application, and you can argue that audittriggers like this are not the way to go (what I find mostly is that auditinformation is stored in a seperate tabel). But this "problem" exists for any updatetrigger, as long as it edits the same table (record) that the user edits through MS Access.
Is there a way around this?