>>>scenario:
>>>If a form is still loading, the user clicked the 'X' of the _SCREEN object.
>>>
>>>Effect:
>>>Abnormal termination of the application which forces to execute the ON SHUTDOWN DO exitprogram routine. The form being opened will not continue loading which gives error: object not found blah...blah...
>>
>>Huh? When my forms load, I can't click anything in the application. IOW< you can't close VFP in the interim, you don't have a usable mouse pointer. I've never seen a VFP application where this wasn't true.
>>
>>I am surprised that the others in this thread seem to confirm the behavior you report.
>>
>>Do you have a DOEVENTS somewhere in your form startup code?
>
>Eric,
>
>To give you more info, below is the hierarchy on how we do things:
>

>SET blah...blah...
>MORE SET blah...blah...
>ON SHUTDOWN DO exitproc
>PUBLIC lLogin, laccess
>lLogin = .T.
>DO WHILE lLogin
>    laccess = .F.
>    DO FORM logsystem TO laccess
>    If laccess
>       DO classtoolbar
>       DO ourmenu.mpr
>    ELSE
>       DO exitproc WITH .F.
>    ENDIF
>    READ EVENTS
>ENDDO
>CLOSE ALL
>CLEAR ALL
>
>PROCEDURE exitproc
>LPARAMETERS lwhattodo
>lLogin = lwhattodo
>more codes here
>CLEAR EVENTS
>

>I don't know we are lacking here. The purpose of the loop is that for the app to just re-do the logsystem, if the user decides to log off only and not to quit the system. The system menu do all the calls whether it's a form or procedure.

In addition, the mousepointer is in HourGlass mode while loading the form, but clicking the 'X' button is still possible which it should not be.