Craig,

Yes, 'as-top-level' will always force modeless as you said. I like the idea of the hidden screen. I'll also try a wait-state.

Thanks,

Irv.

>Irv,
>
>I believe you are already on the right track and it's about as elegant as it gets. Some type of looping structure with an =INKEY(1,"H") or SLEEP API call to keep it from burning all the CPU cycles while you wait for your top-level form to release or do whatever it is you want it to do.
>
>As to the suggestion the Sylvain made about making the form modal, while that won't work with a top level form, you might want to think about taking the _screen object and setting it's top property to something crazy like -4000 or 4000 and then making it visible for a short period of time (user wouldn't see it)... that way you could change the Top-Level form you have to a modal form with Desktop = .T. and AutoCenter = .T. and you would be able to make it modal and still have the same look to your application. It's not an elegant hack, but, depending on your situation, it might work for you.
>
>That's about all I can think of off the top of my head.
>
>>To All:
>>
>>Is there an elegant way to wait for a modeless form to finish before the code continues? It's a top-level calling a top-level form. The called form does some calculations and returns (or sets) some values.
>>
>>I can think of a way by pausing execution, but wondered if there were others.
>>
>>TIA,