Access not closing properly

[Mitch_____W]

I have a 2K BE mdb (on server) which may have, at any given time, 15 connections from 10ea 2K FE mdb's. Many times users have to end the ACCESS process via Task Manager before they can reopen a FE mdb on their box. What is causing ACCESS not to end it's process the last time the user(s) closed the FE(s) they were using last? How can I stop this from ocurring?

Mitch

 

[ghudson]

Killing an Access db via Ctrl+Alt+Del is a great way to corrupt the data [indexes] in your db.

How are your users exiting the db? Are they using a custom Exit button to close the Access application? Here is a command to close the application and the Access shell...

DoCmd.RunCommand acCmdExit

I trust that each user has a copy of the front end installed onto their PC?

Do the users have full permissions to the directory where the back end is located on your server? They need to be able to add/read/edit/delete files where the back end is located. They need to be able to create/edit/delete the record locking file [*.ldb] where the back end is located.

 

[Mitch_____W]

I have witnessed users closing the DB's with the command button with the DoCmd.Runcmd acCmdExit code behind it and it still doesn't sshut down the ACCESS process in the task manager. Doesn't happen all the time though. Could it be a network issue? And I have full permissions set for all users of the DBs' Folders. Also some FE's are local to the user and some FE's are on the server. The BE that all FE's use is on the server as well. I am stumped...

Mitch

Killing an Access db via Ctrl+Alt+Del is a great way to corrupt the data [indexes] in your db.

How are your users exiting the db? Are they using a custom Exit button to close the Access application? Here is a command to close the application and the Access shell...

DoCmd.RunCommand acCmdExit

I trust that each user has a copy of the front end installed onto their PC?

Do the users have full permissions to the directory where the back end is located on your server? They need to be able to add/read/edit/delete files where the back end is located. They need to be able to create/edit/delete the record locking file [*.ldb] where the back end is located.

 

[ghudson]

Does the db compile okay? Have you decompiled it? Have you run a Repair & Compact on it?

 

[Mitch_____W]

I have never compiled any of the FE's. I make changes too often at this point. I have repaired/compacted the DB's frequently. Doesn't seem to make much difference with the occurences...

Mitch

Does the db compile okay? Have you decompiled it? Have you run a Repair & Compact on it?

 

[ghudson]

I have never compiled any of the FE's.

I highly recommend that you compile your db's after any VBA changes are made. It only takes a few seconds to compile your db and it is the best way to let Access catch your coding errors before your users do.

From within any module, click...

Debug / Compile and Save All Modules

 

[The_Doc_Man]

Another issue is whether the .LDB file is updateable at the moment. You cannot exit from Access (cleanly) unless you can remove your locks from the lock database file. Can you tell if something is holding the .LDB file for exclusive use?

 

[Mitch_____W]

I compiled the DB's... no difference in the problem occurance... Not having a problem with the locking file closing (it closes/deletes fine), I am having a problem with the "MSACCESS" process not ending on the user(s) computer...

Mitch

 

[ghudson]

Does the user have the correct file permissions to delete files for where the db is located? The user has to be able to create/edit/delete files for where the front end and back end are located because of the record locking file [*.ldb].

 

[Ade F]

Quitting

Try

DoCmd.Quit

I have had several problems with user not disconnecting from be and app still running. The is a little hardcore but it works for me.

Cheers

Ade

I compiled the DB's... no difference in the problem occurance... Not having a problem with the locking file closing (it closes/deletes fine), I am having a problem with the "MSACCESS" process not ending on the user(s) computer...

Mitch