Hi all,

I've been banging my head over this problem for two hours by now:
I have a modeless form which called another Modal form with a click of a
button:
DO FORM form_b
Messagebox ("This should only appear AFTER form_b is released!")

Is there any way that I could force VFP not to run the messagebox BEFORE
form_b is being released? The messagebox keep on appearing on top of form_b
regardless what I do. In a desperation I tried:
- Change the value of form_b's WindowType Property from Modal to
Modeless
- Put DOEVENT [FORCE] before the 'DO FORM... ' command
- Alter AutoYield property (yes.. I know it has nothing to do with this)
- Put the form in a base class and create an instances instead of 'DO
FORM' it
- Put a bag of ice in my forehead
- Eat a Mars bar
- Drink two cup of coffee

None solve the problem! And this is my last effort: yell for a help in this
ng!

Ideas anyone???

TIA,
Willianto

Re: HELP! How to wait until a form is released (after a DO FORM) to run next code? by Boyd

Boyd
Mon Sep 15 12:57:58 CDT 2003

Did you try a READ EVENTS after the Do Form staement?

Boyd
"Willianto" <willianto@remove-me.telkom-and-me.net> wrote in message
news:#DjoXD7eDHA.1828@TK2MSFTNGP10.phx.gbl...
> Hi all,
>
> I've been banging my head over this problem for two hours by now:
> I have a modeless form which called another Modal form with a click of a
> button:
> DO FORM form_b
> Messagebox ("This should only appear AFTER form_b is released!")
>
> Is there any way that I could force VFP not to run the messagebox BEFORE
> form_b is being released? The messagebox keep on appearing on top of
form_b
> regardless what I do. In a desperation I tried:
> - Change the value of form_b's WindowType Property from Modal to
> Modeless
> - Put DOEVENT [FORCE] before the 'DO FORM... ' command
> - Alter AutoYield property (yes.. I know it has nothing to do with
this)
> - Put the form in a base class and create an instances instead of 'DO
> FORM' it
> - Put a bag of ice in my forehead
> - Eat a Mars bar
> - Drink two cup of coffee
>
> None solve the problem! And this is my last effort: yell for a help in
this
> ng!
>
> Ideas anyone???
>
> TIA,
> Willianto
>
>