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

Sasha_Froyland, when you suggest the need for "migrating away from Access", are you instead suggesting here (or often end up suggesting to clients) updating existing (or developing new) Access database "all-in-one solutions" (complete with forms, queries, reports, macros, tables, data macros, settings, import presets, VBA, and all) and just migrating the *data* to SQL Server (by converting Tables to Linked Tables with SQL Server backend) if/when database size or number of simultaneous users reaches there point to merit it. If so, I am fully on board with that.

However, in many cases where I've seen suggestions or discussions of the need for "migrating from Access", I believe it's worth clarifying that in many cases that does not mean "(fully) migrating away from  Access" or even that "Access can't handle it" since SQL Server-backed Access databases are a very typical use case and type of Access database solution which Microsoft Access is specifically designed to handle well. 

In such cases, I think it's worth emphasizing that you are "optimizing, enhancing their Access or splitting (across types of backends) their database", instead of "redeveloping it" or "migrating completely away from Access", not just for accuracy, but because that plays to Access' strengths, leaving them with the best of both worlds, with SQL Server-backed scalability and performance together with all the benefits of Access, with ease of use/editing/extending/maintenance, as well as its ubiquity and avoided need for vendor-lock-in or need for ongoing reliance on consultants/IT for every change. Though I would suggest engaging consultants for significant changes, the customer can still appreciate the reduced risk and potential cost savings of that not being entirely required in all cases like with custom web apps. 

In short, I suggest that more people refer to "Migrating Access databases to SQL Server backend use for improved performance and multi-user scalability" or "In-place upgrading of Access databases for optimized, scalable SQL Server backend use without requiring re-training or changes to your existing workflows or losing the low-cost, flexibility, and unique end-user-editability advantages that Access provides" or even just "Migrating Access to 'Access + SQL Server' the 'best of both worlds'".