Avoid busy wait in Access 2003
I'm doing a thing in Access 2003 and VBA. I do lots of iteration and sometimes something happens and I would like to halt and notify the user, but not with a MsgBox but in a text field. So, I print a message in it and use a loop that checks a global "hold" boolean. With DoEvents, Windows checks for KeyDown and if it is there, hold is set to False and iteration continues. But, I suspect there is a better way, because isn't that an example of "busy waiting"? Although it is not that "busy", just a boolean check, it is busy enough for my computer to start make sounds, and the overall impression is not robust. Is there a way to just wait (do nothing) and then continue on a key down interrupt?
You do not have to use a msgbox, you can define your own form with a textbox on it and the appropriate code. Open this form with a parameter of acDialog and it will halt the code the same as a msgbox
Counting Rows in a Access Report using letters
Id field (primary key) is skipping numbers of rows that have been deleted, how to change?
Create a Schedule task that run a access file
Does Access 2013 still have an ACE database or equivalent?
Creating 2D (Data Matrix or QR Codes) in MS Access Reports/Forms
Mass Delete Individual Fields
Error on INSERT statement
Microsoft Access 2003 - Expression Builder
Reference existing expression
Automatically updated the textbox
Profiler for MSAccess
Access Switchboard Manager: Invalid Procedure Call or Argument
how should this SQL be written?
Data type for currency values in Access
Update top rows in Access table that match condition
Data type in access 2007