ok to delete ldb file?

  • Thread starter Thread starter julie
  • Start date Start date
J

julie

I know this topic has been covered extensively but none
of the solutions seem to apply to my situation. When one
user gets into the database first then no one else is
able to get into it. They receive the error "The
database has been placed in a state by user 'Admin' on
machine 'xxxxxx' that prevents it from being opened or
locked". Most of the posts that I read said that it was
a rights issue but everyone that accesses this file is in
the same group and this group has full control rights to
the directory where the access file is located and also
full control rights to the file itself. The file sits
out on a network share and I noticed that also sitting
out there was a .ldb file which I thought about deleting
but did not know if that was okay to do. Any suggestions
would be greatly appreciated.
 
If no one has the database open and the ldb file is still there, then it is
ok to delete it. Don't delete it while someone is using the database.

Check to make sure the users are NOT opening the database in Exclusive mode.
There is a setting in Tools|Options to change this by default, but it can
also be controlled from the command line by using the /excl switch or by
using the File|Open dialog and choosing the open options by clicking the
down arrow next to the Open button.

I would start with the Options setting. On the Advanced tab, make sure that
the Default Open Mode is set for Shared. Also, is the person who is locking
everyone out doing edits to the structure of the database (tables, forms,
reports, etc)?
 
It is likely that you have corruptions in your database. Check Tony Toews'
set of articles:

http://www.granite.ab.ca/access/corruptmdbs.htm

Also, make sure you split the database into Front-End and Back-End.

If no one is on the database, you should be able to delete the LDB file
without problem but *make sure* you check the extension TWICE before
deleting.
 
It is only one person who is causing this problem. When
that user gets into the database then no one else can.
If any other person gets into the database first then
everyone else can get into it too. I checked her tools
options advanced and her settings are to share. She is
not doing edits to the structure, just adding data. The
lbd file goes away when everyone closes out of the file
so that is not the problem. Any other suggestions?

Thanks!
Julie
 
If it's just one person, I'd suspect their network privileges on the folder. They need full create, write, update, *and* delete
privileges so that they can delete the ldb file.

See the "Required Folder Privileges" of http://support.microsoft.com/default.aspx?scid=kb;EN-US;299373.

Good luck.

--

Sco

M.L. "Sco" Scofield, MCSD, MCP, MSS, Access MVP, A+
Useful Metric Conversion #16 of 19: 2 monograms = 1 diagram
Miscellaneous Access and VB "stuff" at www.ScoBiz.com
 
Back
Top