The Access Team previously stated that "Access is included in all Office 365 plans and Access 2016 Runtime click-to-run is also available for customers".
This leaves a gap for anyone that has installed a lower version of Office 2019 that does not include Access. The Access 2016 runtime will not install as it is MSI, the Office 365 access runtime will not install as it clashes with Office 2019, which it insists you uninstall.
We are having to tell our customers to not install Office 2019.
So please can we have a runtime that plays nicely with Office 2019

We have some databases with a split front end (stored on local computer) and backend (stored on a server mapped via relative path) using Access 2016 (build 9126.2259). Since upgrading many computers to Windows 10 1803 the backend database constantly becomes corrupt. We have to disable the three caches referenced in the article linked below in order for the corruption to stop, but this makes file server operations much slower while also causing unnecessary network traffic. We never had this issue on Windows 10 1703.

https://docs.microsoft.com/en-us/previous-versions/windows/it-pro/windows-7/ff686200(v=ws.10)

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!!

When a query fails due to data type mismatch or some other field specific error - tell us what field in the error message.

A TreeGrid control could be used in forms, or as just a Tree control. This should be a somewhat customizable look and feel.

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.

It would be great if access form (either overlapped or popup form) has X and Y poperty fixed to active screen (measurement in twips). As far I know, the property LEFT and TOP are relative to their window (most value are 0 if a form in topmost or leftmost.

We had this problem back in August with MSAccess 64 bit on Office 365 crashing after a windows update. Once again, the same issue: Access is crashing multiple times per day because of bugs introduced by Microsoft during the update process.

Faulting application name: MSACCESS.EXE, version: 16.0.11126.20196, time stamp: 0x5c2dc930
Faulting module name: OLEAUT32.dll, version: 10.0.17134.48, time stamp: 0xebd737a3
Exception code: 0xc0000005
Fault offset: 0x000000000008a06d
Faulting process id: 0x1180
Faulting application start time: 0x01d4ac28476e5591
Faulting application path: C:\Program Files\Microsoft Office\Root\Office16\MSACCESS.EXE
Faulting module path: C:\WINDOWS\System32\OLEAUT32.dll
Report Id: 5c83adec-0c56-4e22-b261-5d638b46b548
Faulting package full name:
Faulting package-relative application ID:

I have 2 reports and 1 form open. Each of theses has complex data sources (with many joins, subqueries...). If I open an fourth report - I get the error message.

I think the limits are to low. Please upgrade them.

In a datasheet form we can navigate left/right as well as up/down, navigating between different rows of the recordset.

In continuous forms the up/down errors behave the same as left/right.

Nowadays, to achieve the described behavior we have to catch the KeyDown event in a continuous form and MoveNext or MovePrevious with error handling for first/last record etc.

Instead the behavior should be the same as in datasheet form.
There can be an option similar to "Move after <Enter>".

When you show a query in SQL view the font size is minute. There seems to be no way of enlarging it.

I would like to use the grey background color of Access 2003 and also its blue border color for forms and reports. But now the background color of Access 2016 is white and the border color for forms and reports is white. In Access 2010 you were able to reproduce the 2003 look by setting some options, but that has been removed in Access 2016. Please advise if this capability exists, or please add it.

Export / Import VBA IDE settings (including editor format)

conditional formating is a great feature but slow when data is not small and forms flicker. Can you please improve that?
By the way: Shadows of Buttons flicker too.

In previous versions of Access, I could use Control-A to select all fields in a table within the query design view, then Control-Click on the certain field(s) to de-select. It is not always preferential to use the asterisk, particularly if you are doing something other than a delete query. This used to be supported, but looks like it went away after I upgraded to Office365. Thanks.