We currently have a shared Access database in a Onedrive folder.
User interacts with the file via an excel file with read\write functions. E.g. dbInteract.xlsm
Otherwise, nothing else interacts with the accdb file. The excel file points to a specific accdb file name. E.g. myDb.accdb
Problem arises when (I think) there is an syncing error and one user interacts with the database anyways.
Onedrive creates duplicates of myDb.accdb and names them myDb-user1.accdb etc.
The file myDb-user1.accdb becomes the latest updated file while myDb.accdb remains untouched.
When user retrieves info via dbInteract.xlsm, info retrieved is still from the myDb.accdb file (the file that was not updated). This has created confusion amongst users and they would try to update the database and it reflecting that nothing has changed whilst unknowingly create more accdb files on the Onedrive.
Issue resolves itself once the spare databases has been deleted but was wondering if there can be any preventive measures I can use.