n all versions of Access that I am aware of, going back at least to Access 2000, the escape key cancels queries (whether select, update, append, etc.), and recordset operations (running in VBA).

On the surface this may be fine, but there is a major bug in the implementation: Access "listens" for the escape key regardless of whether it has the focus or not.

So for example, if you have a long running append query and then open Excel, Word, Outlook, or even your browser (any software, presumably), and hit the Escape key to cancel an action in that other software, Access will "hear" it, and cancel your update query!

I've been able to reproduce this bug in Windows 7, 8.1, and 10, with Office 2013 and 2016. This has cost me and my clients hours of lost work. New clients now need to be taught to avoid hitting the escape button under any circumstances. It's a bug that needs fixing right away. This is unacceptable, and it's impossible to believe that Microsoft doesn't know this is going on.

Can we get this reported and given high priority?

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

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

Since 8/1/2018, MS Access has been crashing repeatedly on multiple machines in our office. We are on 64 bit Office 365 and Windows 10. It appears some bug must have been introduced during one of the automatic updates.

This crash appears to occur with automation where I think a second instance of MS Access is calling an MS access program, but not totally sure:

Faulting application name: MSACCESS.EXE, version: 16.0.10325.20118, time stamp: 0x5b64d927
Faulting module name: OLEAUT32.dll, version: 10.0.17134.48, time stamp: 0xebd737a3
Exception code: 0xc0000005
Fault offset: 0x000000000008a283
Faulting process id: 0x32a0
Faulting application start time: 0x01d43fb636a345d3
Faulting application path: C:\Program Files\Microsoft Office\root\Office16\MSACCESS.EXE
Faulting module path: C:\WINDOWS\System32\OLEAUT32.dll
Report Id: b87fac84-eca0-480b-8855-0437a376d7e8
Faulting package full name:
Faulting package-relative application ID:

This crash occurred with conditional formatting in a continuous form

Faulting application name: MSACCESS.EXE, version: 16.0.10325.20082, time stamp: 0x5b524023
Faulting module name: ntdll.dll, version: 10.0.17134.165, time stamp: 0xf4df6dc2
Exception code: 0xc0000374
Fault offset: 0x00000000000f4d1b
Faulting process id: 0x2f34
Faulting application start time: 0x01d42cda8c32b6c7
Faulting application path: C:\Program Files\Microsoft Office\Root\Office16\MSACCESS.EXE
Faulting module path: C:\WINDOWS\SYSTEM32\ntdll.dll
Report Id: cd99d3ff-d7aa-4af6-9385-5db23f91f481
Faulting package full name:
Faulting package-relative application ID:

This crash occurs when we click in a combo box and that box is locked and enabled is set to false:

Faulting application name: MSACCESS.EXE, version: 16.0.10325.20118, time stamp: 0x5b64d927
Faulting module name: mso30win32client.dll, version: 0.0.0.0, time stamp: 0x5b5da093
Exception code: 0xc000041d
Fault offset: 0x000000000009b445
Faulting process id: 0x1178
Faulting application start time: 0x01d43fbb05c2f1a3
Faulting application path: C:\Program Files\Microsoft Office\Root\Office16\MSACCESS.EXE
Faulting module path: C:\Program Files\Common Files\Microsoft Shared\Office16\mso30win32client.dll
Report Id: 2d2299db-57cf-42f3-8ced-5cea27393b1b
Faulting package full name:
Faulting package-relative application ID:

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.

On the off chance that your Outlook OST record has turned out to be broken or unparented due to a few reasons like infection assault, Trojan disease, awful server, Low system property, document assemble activity disappointment, equipment crash or bundle disappointment and you wish to ask back your OST record because of your OST document is in this way fundamental to you, at that point don't freeze you'll have the capacity to endeavor our OST record to PST document gadget bundle furthermore as OST to PST for working environment 2007. In the event that you wish to investigate the work strategy of our OST to PST gadget bundle for Outlook OST to PST for working environment 2007 change then you'll have the capacity to exchange free demo adaptation of OST record to PST document gadget bundle for thirty Email. With the help of ravishing OST specialist program you'll decidedly recapture undecipherable OST go into clear condition. OST to PST extractor program swimmingly convert relocate OST to PST with exact organization. PST, EML, enhancing and markup dialect square measure offered distinctive amid which you will reestablish recouped OST document. "Motivate OST to PST Recovery bundle that profoundly filter out of reach and damage OST messages data then you'll have the capacity to spare OST email into working MS standpoint with another configuration like as:- EML/MSG/EMLX/HTML/TXT/DOC/MBOX and viewpoint profile. This bundle has also capacity to help OST record as:- five.0/5.5/2000/2003/2007/2010/2013 related 2016 moreover in light of the fact that it gives you a development decision to separate noteworthy size of recouped PST document upto 5GB.

Read more information and download free demo version here:- https://www.inspiredatacare.com/convert-ost-to-pst.html

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!

In Access I often use the criteria Intellisense/Builder to help me get the vba string to drill down to a deeply nested subform. But Intellisense/Builder gives up about 3 forms in. It would be nice to be able to drill down further with the help of this tool.
I am by no means an expert at Access but over time have created several useful tools over the years, with the help of many Access experts on line. I created a very comprehensive vacation calendar used by over 200 people (tied to an sql back end) for my employer prior to my retirement. So, any tools that help ease the burden are always appreciated.