Whoops, forgot to put this sample code in...

set talk off
set deleted on
set bell off
set sysmenu off
set multilocks on
set exclusive off
on shutdown quit

clear
_screen.windowstate=2
_screen.caption="My App v1.0, Copyright 2001 West Pointe Enterprises"
_screen.backcolor=rgb(58,110,165)
_screen.minbutton=.F.
_screen.maxbutton=.F.

use mysystfile
if empty(mysystfile.fThisField) then
  if reccount()=0 then
    append blank
  endif  
  do form mysystform to vAbort
  if vAbort=.T. then
    clear events
    quit
  endif  
endif    

do form myinitialform
read events

The MYINITIALFORM fires even when vAbort=.T.

Pete


>Peter
>
>READ EVENTS will effectively wait until CLEAR EVENTS is issued. So what you have done is correct. In the UNLOAD Event on the form, issue CLEAR EVENTS. Any code AFTER the READ EVENTS will then execute.
>
>Kev
>>I have always had a main program that consists of:
>>
>>set talk off
>>set deleted on
>>set bell off
>>set sysmenu off
>>set multilocks on
>>set exclusive off
>>on shutdown quit
>>
>>clear
>>_screen.windowstate=2
>>_screen.caption="My App, Copyright 2001 West Pointe Enterprises"
>>_screen.backcolor=rgb(58,110,165)
>>_screen.minbutton=.F.
>>_screen.maxbutton=.F.
>>
>>do form mbappform
>>read events
>>
>>
>>Should the READ EVENTS be the last item? I guess I don't understand fully what READ EVENTS does. I know it starts "event processing" which I believe is the "processing" of commands, buttons, code, etc.
>>
>>With it AFTER the form I want run... wouldn't that technically not run the code on a form because the READ EVENTS fires AFTER the form? I know this works, but I don't understand why.
>>
>>
>>Is this NORMALLY what is in the main program for an app? What about if I want to do some file manipulation PRIOR to the MBAPPFORM running... I shouldn't put that in here only in the FORM such as in the LOAD or INIT section?
>>
>>Thanks ahead of time for all the great help here!!