"cannot quit visual foxpro"

You can try:

ON SHUTDOWN EXECSCRIPT([on shutdown]+CHR(13)+[on error *]+CHR(13)+[clear events]+CHR(13)+[release all]+CHR(13)+[quit])

pcelba: I don't quite see what you're aiming for.  Your "script" woudl run (a subset of) what is already in my exit routine - which runs already.

jrbblda - that's a very interesting point. I hadn't considered the Modality of the forms. You're probably on the right track. The obvious question, however, is how the hell do I force them to close?

My exit routine already tries to close any open forms with a standard loop

FOR each oFrm in _SCREEN.Forms
      oFrm.abandoned=.t.
      quitting=.t.
      oFrm.Release()
ENDFOR

(I use the two variables to make the forms skip code that I don't want to run if I'm quitting and, yes, I've tried it with and without them and different combinations)

I even thought of including "Thisform.windowtype=0" as a line in the class release code but that isn't permitted (gives an error "WINDOWTYPE IS READ ONLY" at run time.

So how else can we force a modal window to shut?

RELEASE ALL
CLEAR ALL
ON SHUTDOWN
CLEAR EVENTS

The script should close all modal forms.

Rather do ON SHUTDOWN QUIT instead of any more or less fancy script or procedure making any attempts to clear things.

Bye, Olaf.

But ON SHUTDOWN QUIT does not work when modal form exists.

It seems I am wrong... Sorry

Don't worry. I've had this and other worries about a simple QUIT. But in fact it's "stronger" than CLEAR EVENTS and also gives you the chance to do more, as it does release all forms, you run through all the events, eg QueryUnload(). It still has problems with a Messagebox() though, IIRC, but there's little you can do about that.

Bye, Olaf.

Is quitting a public variable?

What I would do is have  cleanup procedure.

It closes everything with TRY CATCH just in case it could not and at the end of it I have a QUIT command.

Hi Tushar,

QUIT does also clear variables in the end, it also closes databases, connections. There are things holding a quit: Messagebox as said, and open transactions. Even ON ERROR * does not suppress the error message. Another reason to handle transactions correctly and as short as possible. You can DO WHILE TXNLEVEL()>0 ROLLBACK ENDDO before QUIT.

QUIT also does not quit immediately, it does cause forms to close and triggers QueryUnload()s. If you have good tidy up code in destroy events of classes and queryunload, unload and destroy of forms, then QUIT does it's job very well.

Cyril,
I don't see that a cleanup procedure can really do more than that. If you finally QUIT after first trying to do what QUIT also does, then you don't gain anything.

Remarks on QUIT in the help:
Always use QUIT to terminate a Visual FoxPro session. If you turn the computer off without issuing QUIT, open files might become damaged and data lost, and temporary work files that would normally be deleted may be left on disk.

One thing you can do additionally in a cleanup or exit procedure is Killprocess, that is, if you get to the line after QUIT. When you use a cleanup procedure, make sure you have it within the main.prg, where it's always on the program stack and therefore can't be "forgotten". Prevent modal states through Messageboxes without timeout. I think print previews can also be a stopper.

Bye, Olaf.

I do a cleanup because my software have Excel, PowerPoint, Word, Outlook, MSProject or any other software open. So I make sure they are closed and the files are either saved or properly gotten rid off. I also clean up the temp directory.

Cryl, okay, QUIT would also destroy references to office and other OLE servers, but itself would not handle any tidy up in them. Still, as I already said twice QUIT does not QUIT directly, it triggers QueryUnload() of forms and Destroy of objects. So these tasks would then need to be part of the classes you have handling office.

You don't need  a cleanup routine as QUIT already triggers all clean up routines in all class instances running. The proof is below.

o = CreateObject("quitcustom")
Quit 
Define Class quitcustom as custom
   Procedure destroy()
      MessageBox("bye")
   EndProc 
EndDefine 
                                              

1:
2:
3:
4:
5:
6:
7: