Try a DOEVENTS in the loop instead of inkey()?
Tristan -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Lew Schwartz Posted At: 11 January 2007 16:50 Posted To: Profox Archive Conversation: Read events, commandbuttons & batch processing loops Subject: Read events, commandbuttons & batch processing loops This is an old story: I have a form that initiates a lengthy batch processing loop. The command buttons on the form are unclickable while the loop is running so I set escape on, test for inkey() in the loop and exit if the user presses escape.... This get me back to my read events statement and the buttons become alive again. This method is as old as the hills and somewhat inelegant. Are there any other or newer suggestions? -Lew -------------------------------------------------------------------------------------------------------------- This email was sent to [EMAIL PROTECTED] Unless otherwise agreed expressly in writing by Marine Software Limited, this communication and attachments are to be treated as confidential and the information in it may not be used or disclosed except for the purpose for which it was sent. If you are not the intended recipient of this communication you should destroy it without copying, disclosing or otherwise using its contents. Please notify the sender immediately of the error. [EMAIL PROTECTED] ------------------------------------------------------------------------------------------------------------------ _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/profox OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
