why does the backend *.laccdb file linger?

[markjkubicki]

i need to occasionally have exclusive to a shared backend file (for routine maintenance ..compact / repair, etc.)


to do this, I...
create a copy of the backend file (filename_TEMP.accd)
then refresh all of the linked tables to it, which i thought would free the original file (filename.accdb)

however, when I check if I can get exclusive access to it, I cannot. And indeed when I check the folder, filename.laccdb (from the initially linked file) is still there.

what gives?
I've checked... no one else has the file open, I have no other instances of ACCESS open that might be using it, I've put a timer in to give pause for the system to clear out the old *.laacdb file...

I'm baffled and will be very thankful for any thoughts, direction, or advice.

Mark

[Beetle]

Do you have full permissions on the shared network folder (Read/Write/Create/Delete)? If you don't have Delete permission than Access cannot delete the lock file when it closes.

[CJ_London]

it may be you have a hidden instance of access still running in the background. Happens to me occasionally when I'm developing and testing code which has taken a wrong turn somewhere so I have to use the task manager to halt the instance. Sometimes I still cannot delete the lccdb file until I reboot.

[isladogs]

So you've refreshed YOUR FE to use the NEW BE file ...BUT it sounds like everyone else using a different copy of the FE will still be linked to the original BE file so it will be locked

The way I do this is as follows:
Create a table in the BE called tblKickout - 2 fields ID (PK) and Kickout (boolean) and just 1 record

Add code to the FE to check the value of that field regularly e.g. every 30 seconds
I do this using the timer event of a hidden form which is always running (and gives a persistent connection)
When the KIckout field is set to true for maintenance work, existing users have a set time e.g. 5 minutes before the FE is automatically closed.
New users won't be able to login.

When all have existed, do your maintenance work then set Kickout = False & inform users the app is available again

[markjkubicki]

... full permission

[markjkubicki]

but once i close the current instance of access, the *.laccdb file is definitely gone
maybe i ought to simple add a line of cod that does delete (seems like a band-aid ...never like band aids)

[markjkubicki]

... full permission