MS Access is just not designed for web based access. It is very easy to corrupt DB. I created a small web app ( not PowerApps ) using Access as a test case and it worked for a few users. I quickly switched over to SQL Server. I also don't trust Excel with PowerApps. I don't consider it a robust business solution. Use Azure SQL DB or SQL Server and Data Gateway.
I agree entirely with @mogulman. I initially moved my Access web app to Sharepoint (one of my tables had 25000 items) but ultimately came down to using Common Data Service as SharePoint could not easily handle that many items. I have been very pleased with CDS with respect to its speed and the number of delegatable functions.
@Drrickryp, I compared CDS and Azure SQL DB. Azure SQL DB better meets my needs:
1. CDS licensing is much more complicated. You need Plan1 and Plan 2 licenses for CDS. For Azure SQL DB you only need a basic license.
2. You can't access CDS from Azure Functions. I use Azure Functions for complex items that are impossible or VERY difficult in PowerApps.
3. You can't execute SQL against CDS.
4. I like SQL Server Management Studio and it connects to Azure SQL DB.
5. You can create other apps (non-PowerApps) and use Azure SQL DB.
6. Azure SQL DB supports views which are very powerful.
7. You can use stored procedures and native SQL against Azure SQL DB using flow.
Stay up tp date on the latest blogs and activities in the community News & Announcements.
Mark your calendars and join us for the next Power Apps Community Call on January 20th, 8a PST
Dive into the Power Platform stack with hands-on sessions and labs, virtually delivered to you by experts and community leaders.
Watch Nick Doelman's session from the 2020 Power Platform Community Conference on demand!