>>

>>if settings bad
>>  launch settings form
>>else
>>  launch regular form
>>endif
>>

>>Or can you check your settings that early?
>
>Yes, I can. But, when the settings form is called, it has to be modal, so I can check to see if the user filled out his settings so I can decide whether or not to launch the main form. I cannot havea modal top-level form, and if the form's showWindow property is "in top-level form", it will not show, because there is no top-level form to show in.
>
>So, in your example, how do you suggest checking what happened in the settings form?

Your settings form would be top-level, also, is the idea. You close it, launch the main TL, and pass the main TL anything it needs when you're done with it...You're in runtime business whichever form is first launched, once the READ EVENTS is established...

In reality, I use a slightly different technique with TLs. There is only one per app, and it does not do any interfacing, serving omly as a better replacement for the main vfp. If used this way, you should have no trouble (except a lot of re-design :) You launch empty TL, bring up modal if needed. Then bring up what you now call your top-level, except it's changed to "in TL"...all form launching is done from a method in the main TL on request from any child forms.

However, for a smaller app I'm designing, I may do something just as I described first above...