Microsoft Ignite 2018 recap: Access team showcases new data visualization features

Even professional SQL Server developers frequently use Microsoft Access for rapid database prototyping, before easily "upscaling" to SQL Server (via SSMA, PowerAccess2SQL, or similar too), as well as even long-term (as a front-end with Forms, Reports, Ad-hoc User-Editable Queries, Import/Export Saved Steps, Macros for their SQL Server database, instead of the order of magnitude greater complexity, cost and delay in developing and maintaining a custom Web App for that.

Microsoft Access was specifically designed to make this "upsizing" to SQL Server process as painless as possible, even including the Upsizing Wizard as a built-in tool (under Database Tools > Move Data > SQL Server) before split off (since Access 2010) into a standalone tool.

Not only does this result in 10x+ lower cost vs. custom Web App + SQL Server development, but use of Microsoft Access is even critical - or the only viable option - in many cases, such as where there are frequently changing business rules/requirements (eg. compensation, tax. etc. calculation rules and forecasting formulas) or where users need to be able to customize themselves (eg. with Financial Analysts or Sales Manager adding/editing fields, ad-hoc queries, data entry-forms, reports, edit calculation formulas and variables, or even links to Excel workbooks/CSV files/data sources) without needing to hire consultants or bring in IT (if they even have dedicated IT staff) for every little change.

However, because SQL Server backend (as well as Split Frontend + Backend databases) complicates making edits and can much increase the cost of development (though still an order of magnitude less expensive than custom web app + SQL Server database, even then) I would suggest delaying until the end or only migrating to SQL Server backend if/when shown to be needed based on daily usage performance, even after optimization. 

Also, like Power Query, Access excels at being a mashup engine where you can combine data from SQL Server (with Tables and Query-like Views as Linked Tables), Web Services, Salesforce, SharePoint, other Access databases and even Excel workbook (preferably in XSLB format) as Linked Tables.