Procedure at Access Stutdown

  • Thread starter Thread starter Jim Evans
  • Start date Start date
J

Jim Evans

Is there a way to assure that a certain procedure is called before Access is
allowed to Quit? I know that there are things you can do such as removing
the Exit option from the File menu and requiring the use of a Logoff form
but, what about the user that just clicks the Close button in the
Application Control Box?
 
Jim Evans said:
Is there a way to assure that a certain procedure is called before Access
is allowed to Quit? I know that there are things you can do such as
removing the Exit option from the File menu and requiring the use of a
Logoff form but, what about the user that just clicks the Close button in
the Application Control Box?
Click to expand...

Call your procedure in the close event of a loaded form (hidden or
otherwise). Access will run the code before unloading the form, then close.
 
Actually, there isn’t.
If you want to ensure a procedure runs then look into running the procedure
at startup.
 
Loss of electrons.
Thermal shutdown.
Application software crash.
Access crash.
Hardisk failure.
CPU failure.
Memory failure.
Network failure.

Each can prevent ensuring code runs.
It’s to do with the definition of ensuring.

If we can do it at startup most, but not all, of the above are ensured.
 
Thanks for your input, Chris.
ChrisO said:
Loss of electrons.
Thermal shutdown.
Application software crash.
Access crash.
Hardisk failure.
CPU failure.
Memory failure.
Network failure.

Each can prevent ensuring code runs.
It's to do with the definition of ensuring.

If we can do it at startup most, but not all, of the above are ensured.
Click to expand...
 
Thanks for your input, Stuart.
Stuart McCall said:
Call your procedure in the close event of a loaded form (hidden or
otherwise). Access will run the code before unloading the form, then
close.
Click to expand...
 
Back
Top