Sometimes CTRL+BREAK or ESCAPE doesn't work, even when Access says you can press CTRL+BREAK or ESCAPE to stop a task. I keep on running into this problem. I suggest better interrupts are programmed into Access that interrupt processing say every 30 seconds to listen to any interrupting key presses that have been made, so execution can be stopped. Fairly frequently, I'm having to crash out of Access to recover control of my computer. Even sometimes, I have to power off my computer completely (without a proper shutdown), to recover control of my computer. These should be simple things for Microsoft to do, to program interrupts for query execution, CTRL+F searches in datasheet mode, column sorts in datasheet mode, and other such things.

When running queries that invoke VBA code, sometimes I can't stop them very easily even though I am able to interrupt the code by pressing CTRL+BREAK. I enter debug mode, choose end execution, but then the code is run again (presumably for the next row in the query). It can be very difficult to get out of this loop-like scenario. Sometimes, changing the code in a function or subroutine procedure such that it is exited as soon as it is entered works to get out of this loop-like situation. However, sometimes, this doesn't even work. This should be fixed. If you gave the user the simple option to also terminate the query, alongside the VBA code interruption, then probably this would solve the problem.

Sometimes when I run a query, it appears to finish but then also appears to not have finished. It's almost as though there is some background processing that carries on after the end of the query. During such time, I'm largely unable to use the Access application. What is happening? It looks like there are some inefficiences somewhere. The query results appear but still Access is busy doing who knows what.