Given the widespread use JSON as a data transport, we should have:

Application.ImportJSON

Application.ExportJSON

like we have:

Application.ImportXML

Application.ExportXML

There are a few libraries out there – replacing these with one or a few lines of code would be extremely useful.

Access database in an inconsistent state....since the release of Windows 10, 1803 our significant percentage of our 3500 customers have consistently lost connection to the back-end database and been forced to stop work during the day to repair their database. Only recently did we discover the leasing fix. In the meantime, our product reputation has been adversely affected. Please release a production update since many of the IT people have refused to make the lanmanserver registry entry and are waiting for the Windows update. HELLO MICROSOFT PLEASE HELP!!

Currently, the developer needs to go through the process of importing a file into a database in order to create or edit an import/export spec in the MSysIMEXSpecs table. True, the MSysIMEXColumns can be edited directly in the table, but overall, the process is not very user friendly. There needs to be functionality to create/edit import/export specs without have to pretend that one is importing an external file.

SQL Server (see https://docs.microsoft.com/en-us/sql/relational-databases/system-stored-procedures/sp-setapprole-transact-sql?view=sql-server-2017) has a great security feature to allow an app to assume a security role when connected to the server. This doesn't work from Access VBA. This leaves us having to give permissions to data that users can subvert. Whilst this can be mitigated, if Access could connect using a user account with no permissions, and switch to an app role with the right permissions security would be wonderful. SetAppRole is particular pleasant in that in the context we still know the original user who started the app.

A frequent task in Access is to import some or all database objects from an existing database into a blank new database. After that, we must painstakingly set all non-standard VBA references in the new database the same way as in the old one.
It would be nice if we could specify in the Import Objects dialog which references should be copied from the existing database into the new one.

Perhaps an error.description2 property which we can reference which stores the error returned from SQL about the true problem. Right now it is very difficult to trouble shoot.

Thanks.

It would be more intuitive to link sql tables WITHOUT the owner prefix.

Since Office Click-to-Run Installs can result in the ODBC / OLE-DB Drivers for ACE NOT being visible to the system outside of the VDI install environment, we need a CURRENT version of the ACE engine redistributable package (the last one being from Access 2010 - 6 YEARS AGO!)

For more info see: https://support.microsoft.com/en-us/kb/2874601

When I try to export an Access table into an Oracle database it doesn't retain the input field formats. Everything is converted into a string and the indices are lost. I've contacted Microsoft about this before but got no meaningful response, presumably for petty proprietary reasons.

In a frontend/backend scenario with linked tables to a password secured Access backend the password can be figured out. It is human readable in the Connect field of the MSysObjects table in the frontend. Please prevent this by encryption.

When importing delimited text (e.g. CSV) one can indicate that the first row contains column headings.
This ability does not exist for fixed width text. It should, to make the feature more useful and consistent.

Display Excel Table names in the Wizard when loading/linking external Excel data, currently only specific name range or the spreadsheet is visible.

in office access 2007 we used to be able to import text files that have an extension other than .txt, many businesses have files that are text files that do not have .txt extension and although I can change the extension to .txt, it is very time consuming when I have thousands of these files

There seems to be no way of allowing Access to link to an Azure SQL database where Azure Active Directory Multi-Factor Authentication has been enabled. This means that if an IT department switches on MFA Access can't connect to an Azure SQL database it can connect to where MFA has not been activated.

If I have missed something, please tell me!

We are currently developing and testing a dotnet interop app that allows an Access frontend to integrate with QBO via API calls, and was wondering if you would be interested creating a QBO data connector.

Develop a version of access that can be run on a lightweight android device or an application that can be run from the cloud.

Create a link to Outlook WebApp contacts folder.
The connector already existing depends on an Outlook PC/MAC version to get the data from. I suggest creating a connector directly to the contact's server folder.
That way it would be possible to edit easily a list of Outlook WebApp contacts in Access.