Microsoft Access is purely a desktop application, meaning it can only work on the desktop, not in a web browser. It is solely meant to be run on a local wired network. Although in theory the database can be uploaded and stored in SharePoint or OneDrive, it cannot be used in a web browser (you will always be prompted to download, work offline and then upload).
Here are your options when dealing with MS Access and O365.
1. Store the MS Access DB in SharePoint or OneDrive and work offline
In this case you will download a copy when you need to open or update the db and then manually re-upload to SharePoint. In this scenario O365 is used purely as a backup storage location since a separate copy will still exist on the user's desktop. Recommended only when a single user is using Access.
2. Store the MS Access DB in SharePoint or OneDrive and Sync the library
Follow these steps to Sync the library where the database is being stored: https://uthrprod.service-now.com/sp?id=kb_article&sysparm_article=KB0010710. Now, open the database through Windows Explorer or Finder under the Sync'd location. Changes made to the database will be sync'd back to SharePoint as long as you are connected.
If you are working with a shared database, this may be problematic as each user will need to sync locally. It is possible that in a very active database changes are not properly merged. Also, as the database will be residing on the desktop, if the database is very large it could easily exceed the amount of space required. Not recommended for shared databases.
3. Convert the MS Access DB to SharePoint Lists
In this case, you will entirely eliminate the use Access by re-creating the Access tables as SharePoint Lists and use the out of the box functionality to work with Lists in a web browser. This is recommended for simple databases only. You are limited to the SharePoint List interface and capabilities.
4. Use MS Access as the front end interface but move data tables to SharePoint Lists
In this scenario you will switch your Access tables to use SharePoint as a datasource, but still continue to use Access as the front end or entry point. In this case, you will need to re-distribute the Access front end (accdb) to all the users any time you make changes to the interface or forms. But the data will be stored in SharePoint and updated in real-time. For more information on this please see the following: https://www.youtube.com/watch?v=b2bb_3Wg80g