>>>Thanks for the suggestions everyone. None of it helped<vbg>, but thanks!
>>>
>>>If the called form is modal, modeless, in screen, top level, etc., it still works the same: The called form displays, let's me enter stuff and press Save. Save saves and the form is released. All fine except that the calling code that I want to get some info from the called form has cheerfully moved on with it's life and can no longer make use of the called form info.
>>>
>>>I know I did this a zillion times in FP 1.0 and later. Time to find and dust off the old books I suppose.
>>>
>>>Thanks guys,
>>>
>>>Gary
>>
>>Gary,
>>Call Modal from FROM modeless one, and DO NOT make that modal form TOP LEVEL.
>
>Or... if there's a top level form which should behave like modal (i.e. pass values to other places when closed), then the code responsible for the modal behavior (passing them pesky values) should be in the form, not in the caller.
>
>So, Gary, move the code which was supposed to run when the form exits somewhere into that form's .unload() or (better) into some custom method which will be called when user clicks OK.

It depends of what Gary needs, sometimes modal form is mandatory. Nothing should happen during the execution of that form.