[Last Call] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 736
  • Last Modified:

Unable to remove .laacdb file

I am unable to remove a .laccdb file.  Says it's in use by another program.  Checking open files it does not appear to be open.  Tried to use appuser, but does not work for the 2007 file format.  Thoughts?
0
Kram80
Asked:
Kram80
  • 4
  • 3
  • 2
  • +2
1 Solution
 
Jim Dettman (Microsoft MVP/ EE MVE)PresidentCommented:
<<  Thoughts? >>

 A reboot is the simplest.  If that is not possible, there are other methods, which I can post if needed.

Jim.
0
 
Kram80Author Commented:
Yeah, if you could.  The db is actually on a SAN.  I was surprisingly able to connect to it via computer management to see the open files.
0
 
NorieCommented:
Have you tried reopening the database and closing it again?

Always seems to work for me, though if you didn't open the database in the first place
it might be locked by another user.
0
NFR key for Veeam Agent for Linux

Veeam is happy to provide a free NFR license for one year.  It allows for the non‑production use and valid for five workstations and two servers. Veeam Agent for Linux is a simple backup tool for your Linux installations, both on‑premises and in the public cloud.

 
HainKurtSr. System AnalystCommented:
try to fix/repair/compact db...
0
 
Kram80Author Commented:
Yeah, tried that.  It changes the modified date/time, but will not remove the file upon closing the db.
0
 
Kram80Author Commented:
compact and repair didn't do the trick.
0
 
HainKurtSr. System AnalystCommented:
http://office.microsoft.com/en-us/access-help/introduction-to-the-access-2007-file-format-HA010067831.aspx

Locking files are deleted automatically when all users close the database.

So, make sure all users are disconnected then manually delete the file... then re-open it...
0
 
NorieCommented:
You can find out if the lock is for other users by opening the laccdb file in a text editor.

That won't solve the problem obviously but it might give some idea of what's going on.

0
 
Kram80Author Commented:
I had the person reporting the problem reboot all PCs that could be connected to it.  Unless he missed one.  Strange thing is I'm not seeing anyone that has the file open when looking at open files.  When I open the db, I see I have it open but it clears when I close the db.

I'm not very familiar with access, but what is a .laccdb file?  I understand it's a locking file, but I'm able to open the db fine.  Would it be locking them from doing changes?
0
 
HainKurtSr. System AnalystCommented:
it prevents deleting/renaming file... read the relevant paragraph that I send before...
0
 
Scott McDaniel (Microsoft Access MVP - EE MVE )Infotrakker SoftwareCommented:
The Access lockfile is used for several things, but the main task is to handle record-locking in a Jet (i.e. Access 2003 or earlier) or ACE (Access 2007/2010) database.

See this article: http://support.microsoft.com/kb/299373/EN-US. It is specific to 2002, but the same concepts apply to .laccdb files as well.

" Would it be locking them from doing changes"

What sort of changes? Multiple users can make DATA changes at the same time (assuming they're not working on the same set of data, of course). However, if you're referring to DESIGN changes (like adding a Report, modifying a Query, etc), then only ONE user can do this.

0
 
Jim Dettman (Microsoft MVP/ EE MVE)PresidentCommented:
<<I had the person reporting the problem reboot all PCs that could be connected to it.  Unless he missed one.  Strange thing is I'm not seeing anyone that has the file open when looking at open files.  When I open the db, I see I have it open but it clears when I close the db.>>

  That's not going to help.  It's the SAN OS that holds the locks for client stations.  What you most likely have is a client that dis-connected abnormally, and the SAN OS is still holding the lock.

  If this were windows, I could tell you how to delete the file handle, which would allow you to then delete the LDB file.

  With your SAN, if you have any type of utility to close network sessions, then you should for all the users that might have been using the app.  Or possibly an open file display, which let's you close the files.

 Outside of that, it's a reboot.

Jim.
0

Featured Post

Transaction-level recovery for Oracle database

Veeam Explore for Oracle delivers low RTOs and RPOs with agentless transaction log backup and transaction-level recovery of Oracle databases. You can restore the database to a precise point in time, even to a specific transaction.

  • 4
  • 3
  • 2
  • +2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now