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
How should I lock the table in this VB6 / Access application?
insert records with request.form gives me JET error 80040e14
How can i compare same field in 2 different tables when it match or likes?
Access 2007 Textbox Date Formatting
table locked or in use when calling RunSQL
MS Access = referencing a control that is within a sub form
Get Name of Current VBA Function
MS Access 2010: How do forms communicate values to each other?
MSAccess - populate text box with value from query
How do I revert to default System.mdw after doing a SetDefaultWorkgroupFile?
ms-access 2007 runtime and lockWindowUpdate
Show Report Pages Count Only On Print
Custom Record Navigation
How to lock specific rows in a subform when a form loads?
If [ComboBox] Is Null Statement in VBA/Access 2007
Check Microsoft Access Form Values before Save