Hi Jess,
I haven't noticed the issue with _SCREEN(X), but I think this issue is common: How does one release the app cleanly when there may be ongoing code?
My ON SHUTDOWN does an ThisApp.Release(). The release of the app is a two part process. When Release is called, I start a timer, set a flag, and cancel any model forms. This allows the processing to end, and then the timer can fire the final release. This time, since the flag is set, we know it's safe to REALLY release the app.
Charlie

>>>>We do have ON SHUTDOWN DO ExitProc, but the trouble is when calling a form via menu (whole app has been loaded at this point), and it has a wait state while loading - DE tables, the user have the tendency to click the 'X' which causes the error.
>>
>>One of the nice reasons to use Top-levels, so you can control this behavior completely (sorry, not much help otherwise :)
>
>Bruce,
>
>It's funny because we already deployed a lot of our applications to several clients, and this morning, one of our QA personnel deliverately click the _SCREEN.Close button while loading a form, and there, the story started... Well, that incident is rare to happen and it has no major impact, but still, it's being considered a bug. We are thinking of setting _SCREEN.Closable = .T. but trying to look at it, it's not a good idea. The app is becoming cheap...