The Access team is adjusting our status for this request – we are planning to embed the Monaco Editor (support for SQL Editor improvements) into Access, to be released within the next semester (first half of 2021), which will provide capabilities such as syntax highlighting, IntelliSense, SQL comments, and more. We are excited to have this capability released by next year, and we appreciate the energy and enthusiasm on this feature request. We still have a long ways to go to improve our experience with SQL, so please stay tuned as we execute on this objective!
Thank you for your feedback.
In terms of setting SQL Server as the default database format, that is currently not in scope for the Access product. We have provided and will continue to provide efficient methods to integrate your Access data with SQL server, and the team will continue to develop more features that streamline the data migration experience (see https://support.office.com/en-us/article/migrate-an-access-database-to-sql-server-7bac0438-498a-4f53-b17b-cc22fc42c979)
However, the ACE database engine has and will continue to be Access’s central data storage unit.
There are new features coming soon that will improve the Access: SQL experience, and we are excited to share this news. Please stay tuned! :)
An error occurred while saving the commentChristopher Cookson commented
I don't think SQL Express is necessarily needed, as with increasing cloud data usage, there's a strong case for SQL Azure if you need multi-user capability, but want to retain the rich client capabilities that Access desktop has over Access web apps.
It would be nice to have a 'Publish to SQL Azure' option.