I have developed a SQLServer 2016 database hosted by a web hotel, using latest version of Access on my Win11 PC as front-end, connected by ODBC. This works without any error-messages.
I want to migrate a copy of the SQLServer db to a MySQL/MariaDb and use the same front-end.
I have migrated the database to a MariaDb server hosted by the same web hotel, and ensured that the different tables’ timestamp field have been set to ‘timestamp’, ‘no nulls’, default ‘current_timestamp’. Having re-connected using the lates ODBC driver for MariaDB.
All queries/views used by the Access forms are stored in the Access front-end only.
I open the front-end. No errors! I open a continueous form based on one table only, and I get an ‘write conflict’ followed by an Access 3197-error message. The same error-massage appears if I try to run a procedure updating the data. Opening the same table directly in Access ‘table view’, no conflict. I open the table with an SQL query in phpadmin; no conflict.

I carried out the same exercise, but now migrating the db to a MySQL server on my PC (‘localhost’). The same ‘write-conflict’-message appears.
I take it that the record locking strategies are different in MySQL/MariaDb and SQLServer.
My question is, what may I do to remedy my problems with respect to using MariaDb/MySQL as server?

Gerhard