Access reopens after Application.Quit

  • Thread starter Thread starter Mark Moore
  • Start date Start date
M

Mark Moore

I'm not sure if this is the correct place to post this,
but i'm at my wits end.
I have an Access application that I built and on the main
form I have an Exit Database button that runs the
Application.Quit - I have used this in numerous other dbs
to exit the application adn Access. However, in this
particular db, once it colses/exits, Access immediately
reopens with a blank screen and it maintains the ldb file
showing the user/device as being logged into the db. The
only way to close the newly opened session of access is to
terminate it form the Win Task Manager.
I have no security on the db, but it is split in to a
front end and back end. The back end contains only the
tables. I'm using Access 2002 format for the FE and 97 for
the BE because I have a 97 version of the same db (with no
problems). I have checked to make sure there are no broken
references and I have also ran repair/compact.

Please provide any possible fixes - Thanks!
Mark
 
Mark said:
I'm not sure if this is the correct place to post this,
but i'm at my wits end.
I have an Access application that I built and on the main
form I have an Exit Database button that runs the
Application.Quit - I have used this in numerous other dbs
to exit the application adn Access. However, in this
particular db, once it colses/exits, Access immediately
reopens with a blank screen and it maintains the ldb file
showing the user/device as being logged into the db. The
only way to close the newly opened session of access is to
terminate it form the Win Task Manager.
I have no security on the db, but it is split in to a
front end and back end. The back end contains only the
tables. I'm using Access 2002 format for the FE and 97 for
the BE because I have a 97 version of the same db (with no
problems). I have checked to make sure there are no broken
references and I have also ran repair/compact.
Click to expand...


That behavior is usually (but not alwways) because you have
left an object reference in such a state that Access thinks
there is still something going on in your program. The kind
of reference might be as simple as opening a recordset but
never closing it and setting the object variable to Nothing,
Check throughout your code to verify that you Close every
object that you open. Also, make sure that all object
variables are set to Nothing when you're done using it.
 
How stupid - I created a global function that opens a
recordset and never closed it.

Thanks,
Mark
 
Back
Top