Hey Steve,

Sorry about that! I can't believe I labeled the whole thread incorrectly!

The modal splash screen doesn't go away, it just drops behind the modeless screen. We've been running in an environment where all our forms have been modal and I'm looking for a way to begin using modeless screens within the same framework. So, down the road, we may have to change the way the splash screen works. Basically, it only goes away when the whole app is shut down.

The read events is definitely happening, I have traced stuff that far.

When the form immediately closes, the menu is still active and our app up and running ... its just that one form that closes down.

Great suggestion with the do form right from the menu! I'll give that a shot.

In tracing through my stuff today, I'm beginning to wonder if our framework is the culprit ... I'll need to hear back from Lloyd in regards to where control goes after a modeless form is instantiated.

What I'm wondering is if a modal form maintains "focus" until it closes and then returns control back to the program that instantiated it while a modeless form returns control back right away and allows the program to continue running. If this is the case, that may be causing the problem. Tracing through the code, it looks like this may be the case.

>>No, my ShowWindow property is set to 0 (In-screen). My WindowType property is set to 0 (Modeless).
>>
>
>Oh, your thread title says "Modal form" :)
>
>>I should've mentioned this earlier. Our program starts with hqmain.prg that builds a menu, launches a modal form (as a splash screen) and issues a read events.
>>
>
>What code or action makes the modal splash screen go away? Have you traced throudh the code to ensure that the READ EVENTS is actually happening?
>
>Also, what happens when the form doesn't run...does the application completely close down, or is the menu still active after that point?
>
>>Selecting a menu option launches a second program which in turn launches a third program called p_brform. (I know it seems ugly but it's legacy code that just won't die.)
>>
>
>Have you added a simple DO FORM to the menu, and have it run a simple modeless form to see if the problem exists in that scenario?
>
>I'm out of questions for now. :)