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
Allow MDB Downloads in IIS7
Possible to set filter on subform from parent form before subform data loads
Access sorting by 'revision date' of 'individual widget' by customer
Is there a Windows 7 ODBC driver for Access?
Using parameter queries in expressionbuilder in access 2007
Convert date from access to SQL Server with SSIS
Access 2000 Forms - open center screen?
Converting DAO to ADO
Printing an Access report and decimal place weirdness
Extract OLE object containg images using VBscript
ms access query results display problems
Record cannot be read; no read permission on 'MSysObjects'
VBA “delete” button in MS Access 2007
MS Access Typecasting Number to Double
Macro across multiple word documents
MS Access tables match and synchronize