I don’t work directly as an Access developer but do some basic aspects of development and administration for an MSACCESS application with central accdb backend (currently based on Access 2016) that is located a Windows server file share.
Users access and update data in the system via their own front end accdb files from their own personal folders on the same \\server\share. There is a corporate project to migrate all our file share data (located on a standard windows 2016 file server VM) to SharePoint Online within our 365 tenancy, which will include the backend and frontend database files as well as thousands of other files.
The application has been developed over a number of years using multiple versions of Access. In your experience, are such apps ‘geared’ for an easy migration onto SharePoint online, or would they probably require a complete re-development in order for them to work? We may be able to put forward a business case for keeping those files on a traditional file server, based on your feedback on how painful an exercise this may be.
If you have been tasked with similar, what we the key amendments required in making the application (front and back end components) SharePoint online 'ready'? I appreciate it will be a case by case basis but any general thoughts and feedback would be interesting. The Microsoft planning documents for migrating files from file shares to SharePoint/OneDrive only really cover troublesome issues such as file extensions, characters in file paths, limits of file/folder characters etc), and no specifics really on access database applications and the work required to make them work on SharePoint online.