Wondering whether anyone else has experienced occasional GPFs following
Application.Quit calls?

I call Application.Quit from my own Shutdown() routine.  In this routine
I've tried being as complete as possible - cleared all module-level and
global variables, closed all forms, reset all the toolbars, did a
dbEngine.Idle, a couple of DoEvents for good measure, but I still
occasionally get this (with both the full and runtime versions of Access
97).  I've never gotten it by closing Access via the close button in the
upper-right of the MDI frame, only when calling Application.Quit via my
ShutDown() routine (from a form button or my File/Exit menu item).  BTW,
modifying the parameter to Application.Quit doesn't seem to help.

It's tough to deal with because it doesn't happen everytime.  It doesn't
appear to be related to any of my application's activities, as I can get it
by exiting immediately after my database is opened (it auto-loads a
splash-style form which executes a Startup() routine which verifies some
things about the database and then displays another form).  But I don't get
it everytime, and I don't seem to get it more than once.  In other words,
once it happens, it never happens again until I reboot the PC.

Also, it happens in an odd way.  Immediately following the Application.Quit
call, Access minimizes itself, then, just as it disappears from the Start
Menu bar, the GPF window appears.  Is this minimizing behavior related to
the shutdown problem I've read about here and have personally experienced,
whereby Access won't quit but instead only minimizes itself?

I've searched the MS KnowledgeBase with no luck.

I've reproduced it on Win95 (OEM 2) and NT (v4.0 SP 3) PCs.  I'm using the
latest Access 97 system, with all patches and updates (including a recent
update to JET 3.51).  It happens with both the full and run-time versions
of Access 97.

Any help (or confirmation of this behavior) would be appreciated.  Thanks.

ewb

Are you, in any of your forms, addressing a check box as
Forms!FormName.CheckBoxName in an evaluation, such as an If Then statement
??  If so,  see if you can duplicate the error consistently by opening your
mdb and running this evaluation statement before using .QUIT.

If you can duplicate the problem,  then try changing the syntax to
Forms!FormName!CheckBoxName and see if the problem still exists.

HTH
--
Dev Ashish (Just my $.001)
---------------
The Access Web ( http://home.att.net/~dashish )
---------------

:Wondering whether anyone else has experienced occasional GPFs following
:Application.Quit calls?
:
:I call Application.Quit from my own Shutdown() routine.  In this routine
:I've tried being as complete as possible - cleared all module-level and
:global variables, closed all forms, reset all the toolbars, did a
:dbEngine.Idle, a couple of DoEvents for good measure, but I still
:occasionally get this (with both the full and runtime versions of Access
:97).  I've never gotten it by closing Access via the close button in the
:upper-right of the MDI frame, only when calling Application.Quit via my
:ShutDown() routine (from a form button or my File/Exit menu item).  BTW,
:modifying the parameter to Application.Quit doesn't seem to help.
:
:It's tough to deal with because it doesn't happen everytime.  It doesn't
:appear to be related to any of my application's activities, as I can get it
:by exiting immediately after my database is opened (it auto-loads a
:splash-style form which executes a Startup() routine which verifies some
:things about the database and then displays another form).  But I don't get
:it everytime, and I don't seem to get it more than once.  In other words,
:once it happens, it never happens again until I reboot the PC.
:
:Also, it happens in an odd way.  Immediately following the Application.Quit
:call, Access minimizes itself, then, just as it disappears from the Start
:Menu bar, the GPF window appears.  Is this minimizing behavior related to
:the shutdown problem I've read about here and have personally experienced,
:whereby Access won't quit but instead only minimizes itself?
:
:I've searched the MS KnowledgeBase with no luck.
:
:I've reproduced it on Win95 (OEM 2) and NT (v4.0 SP 3) PCs.  I'm using the
:latest Access 97 system, with all patches and updates (including a recent
:update to JET 3.51).  It happens with both the full and run-time versions
:of Access 97.
:
:Any help (or confirmation of this behavior) would be appreciated.  Thanks.
:
:ewb
:

Eric,

I have seen the exact same thing in my app, although it's without a GPF.
Often while I was designing, I would attempt to close the database using
either the Exit command from the file menu, or a Quit method in my VBA.
Sometimes Access 97 would close the database, but it would only minimize the
Access window.  I could never get it to close successfully - I always had to
terminiate the app on my own.

Yes, it's extremely frustrating.  I noticed that the behavior didn't surface
when I wasn't altering the design of the database (i.e., only opened the
database to work directly in the foms and such).

If you find any more information, please let me know!

Thanks, Matt.