Rod,

No problem :)

When the program runs the modeless form, the code in that program continues and falls right off the bottom. That's why I asked you what you would gain by having an object associated with a modeless form. You can demonstrate this to yourself by adding a couple of lines to the end of that program (after it has run the form), and you'll see what happens:

ACTIVATE SCREEN
? PROGRAM()
WAIT

The object itself (to answer your question to Lloyd), would be PRIVATE in scope (by default).

>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.
>