>>>>A very simple way to accomplish this is to make the form MODAL. Once the modal form is called the code from the calling form will not continue to run until the MODAL form is released.
>>>>
>>>>Michael G. Emmons
>>>>
>>>>>OK, I have been doing this for awhile now, but just have not run into this before. My code is
>>>>>Do FORM myform
>>>>>DO Procedure
>>>>>DO procedure 2
>>>>>etc...
>>>>>
>>>
>>>Not true. Modal forms will only allow input into the current form true, but execution of code in the method that called the form doesn't stop.
>>
>>
>>are you sure? maybe i have been working with visual basic for too long.
>
>I think you were right in the first place. Just did a quick test. I had a "modeless" form1 containing a command button. The "click" method of the button calls a "modal" form2 and is followed by a "wait window" statement. During execution, the message associated with the "wait window" statement in form1 did not show up until after the "modal" form2 was closed.
>
>Paul

thanks. for a minute, i thought i was going to have to switch companies to get back to a sane language...