Charlie,
I made it work by specifying the form to close: CLOSEWINDOW FORM1 Claudine :-) _____ From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of Charles Parks Sent: Wednesday, March 19, 2008 11:33 AM To: RBASE-L Mailing List Subject: [RBASE-L] - RE: MDI form and waiting I haven't tried that because it is my understanding that as the MDI form is opened that the next line in the command file is ran regardless of the MDI form's state so there would need to be some sort of loop to keep checking on the value. I tried removing the MDI portion of the call but the variable's value isn't changed then. _____ From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of Claudine Robbins Posted At: Wednesday, March 19, 2008 11:23 AM Posted To: RB7-L Conversation: [RBASE-L] - RE: MDI form and waiting Subject: [RBASE-L] - RE: MDI form and waiting Charlie, Have you tried replacing your while loop with a simple if/endif? Claudine :-) _____ From: [email protected] [mailto:[EMAIL PROTECTED] On Behalf Of Charles Parks Sent: Wednesday, March 19, 2008 11:15 AM To: RBASE-L Mailing List Subject: [RBASE-L] - MDI form and waiting If a variable value is being set in a different form opened with a MDI option is there a way to wait until that value has been set been set before calling the next line of code in the calling form? The following works in tracing but locks up in running mode. set var vVariableInForm1 text = 'False' EDIT USING Form1 MDI AS Form1 --vVariableInForm1 will be set to true in this form and the form will be closed with CloseWindow while vVariableInForm1 = 'False' then ... --some code to check vVariableInForm1's value. endwhile ... --Continue with calling form's code. Is there a pause timer shorter than 1?
