I know that this idea has been floated twice before and I also note that the Access team have responded and indicated that this is not part of the development and I also note that its been closed so more votes cannot be taken on it. Thought it was important to re-open because its actually quite a popular idea. I understand that SQL Server / SQL Azure or SQL Express are the way to go if users are wanting larger backends but for quick and dirty working for ETL projects or random data analysis of large datasets individuals may not wish to have the additional overhead of enterprise grade backend database install. Remember a basic SQL Server install will require SSMS and the SQL engine ontop of Access - For individuals in large organisations this may require petitioning central IT for a number of weeks or months. I would always recommend using SQL as the backend for even smaller projects but increasing the max file size would just make Access even more flexible. Anyway keep up the good work MS

I would like to suggest to Microsoft an idea that came to me in a dream last night. My dream was a little bit like:
I was sitting in a bench at some park, there was no black people around, Donald Trump probably won the reelection. I was reading the news, "Elon Musk dies on his way to the sun"... For some reason I'm not surprised. All of the sudden I realize I was supposed to go to work because its sunday! I rush to McDonalds... on my way I see a massive screen showing the new capabilities of Access 2079 -"Amazing integration with Office 2007, Incomparable speed on deprecated processors, Almost ready for Hidpi, Still $100 a licence"
I'm in shock, this is not a dream, its a nightmare... this is the future and Access is still around, and MVPs from the 90s manage to put their brains inside machines so they could still scam people with their creations...

Please, deprecate Access, lets not fool each other, the only reason Access is still around is the same reason dBase and Cardbox and other near abandonware products are still around, because theres an old userbase that will rather die than to move into any newer technology and they serve a large number of small businesses in the PAST!

It has to go... think about it as a catastrophic incident, no one wants it to happen but it will happen, and if it happens people will just have to live with it. Just like Sharepoint, just like Silverlight...

ACCDE files provide significant security especially if combined with password protection, disabling shift bypass, hiding navigation pane/ribbon/application window, using a SQL Server backend etc.
Doing so prevents users importing forms/reports & of course code from another database. However, a major weakness & common complaint is that users can still import all tables & queries including hidden & system tables.
It is possible to make tables 'deep hidden' to prevent this ...but even that can be reversed ...if you know how.
Please add code to prevent this security loophole using VBA (not in the ribbon!). If users lock themselves out by doing so, they only have themselves to blame

Give us the ability to request a partial Compress & Repair at the table level within an opened database.
It should not be impossible to compress database records and disk pages at the table level, bypassing and freeing up any space no longer needed for deleted data records and index entries.
Given Microsoft refusal to consider revamping the database Access database files to allow for larger databases, then giving us the ability to better manage the available 2GB of space by making incremental requests to compress & repair thins partially at the table-level could be a meaningful compromise. This could allow us to enable "paging-style" approaches with which to attack larger data files and import/export tasks which are presently beyond the reach of MS-Access databases.

We have a webservice on which we have a PowerApp connector that enables PowerApps to run any macro, vba procedure/function, opening of a form to fill in text-fields and/or perform the equivalent to buttonclick-events in an Access Application. If MS-Access out of the box could configure and enable a webservice on the machine it's running and thus would enable a PowerApp to be a cloudfirst/mobilefirst frontend presentation layer, MS-Access 2019 would really become something new. When the Access application has linked SQL-tables to SQL-2016 or up, it can easily delegate the creation of JSON to SQL-server, but I wouldn't be surprised VBA already has JSON functionality in Access 2019.

Please raise the allowed and supported password length to at least 20 characters (as in Access 2007).

For security reasons our company releases a new security guideline so that every relevant application has to use passwords at least 20 characters long.
This would mean several hundred password encrypted databases from various versions of access are no longer allowed to be used.

Technically it is possible to use a 20 character long password within a database (backwards compatibility). But this doesn't work with linked objects. The Connect-String in MSysObjects stays empty.
The use of more than 14 characters is not supported by Microsoft right now.

Access needs a quick way to get a good solid installation of Back-end and Front-end databases including a registry edit for Trusted locations and versioning.
It should also include the ability to:
Add Icons,
Add Desktop and other shortcuts,
Allow user to accept an ELUA (End User License Agreement)
Run simple scripts,
Install with full windows trust. (maybe with a certificate?)
An uninstaller.
A check for updates function.
Install support files into specified folders.
Read simple system values and react accordingly (eg if 64bit systems then install 64 bit ODBC Driver)

Also it would be nice if it could notify the user of a new application Version (via a Web ini file or similar?)
Optionally install the Access Runtime.

This would lead to massive time saving for developers and make installations quick and identical across many users...

SQL is something that I find particularly useful when I am running a database. However, the SQL user interface is very poor in my opinion. It should be more something like the Visual Basic interface, where when you start typing in a formula, then it has a dropdown with all your options and when you select the function from the dropdown, it will show you how to build the formula. For me it becomes very time consuming to have to go online to figure out how the function is built. Also it would be great if it can be colour coded. There should also be more SQL functions that should be made available to the user, like in Microsoft SQL.
Also, being unable to comment directly into the SQL code is something I am finding annoying because I would like to be able to explain to future users what certain pieces of SQL code are for. I would appreciate if you could implement these ideas in the next version of MS Office. Thanks!

Old versions of office allowed users to install on any hard drive they wanted. The current office 2016 consumes up valuable hard drive space for the Operating System. Allow the user to decide where they want it installed. To make it easy have a express or custom option for installation. I have seen many companies use this option it allows easy installation for those who are less tech savvy and those who have experience to customize their installation. I use Visual Studio 2017 and it allows an installation option. THIS IS A MUST most people have small hard drives for the OS especially SSD which are about 140 GB which is OK for an OS itself.