close DB

  • Thread starter Thread starter dimpie
  • Start date Start date
The existence of an .ldb file indicates that one or more users has the
associate .mdb file open. Under normal circumstance, the .ldb will disappear
when the last user closes the .mdb, but sometimes an .ldb gets orphaned. You
can delete the .ldb IF YOU ARE SURE that no one has the .mdb open - otherwise
serious database corruption will ensue.
 
How can i close a DB (.ldb), so i can open with editing rights?
Click to expand...

ummm...

A .ldb is not a database. It's the record-locking file which Access creates
and opens automatically, and deletes when the last user closes the database.
It has nothing specific to do with "editing rights" (other than it prevents
two users from editing the same record at the same time).

What specifically are you trying to do, and what problem are you having? I'm
sure there's a solution - but it doesn't involve "closing a .ldb".
 
I created this DB that is used by several people. Here are my questions..

How can i made it multiuser?
How can i open with admin rights when others have it open?

Thanks a lot for your help.
 
I created this DB that is used by several people. Here are my questions..

How can i made it multiuser?
Click to expand...

It's multiuser out of the box. You don't need to do anything.
How can i open with admin rights when others have it open?
Click to expand...

Open it; if you have security implemented, open it with an account with admin
privileges.

What you can't do is have two people making *DESIGN CHANGES* to the structure
of the database simultaneously.

For a multiuser database you really should use the Database Splitter Wizard to
split the database into a shared backend containing the tables, and a frontend
containing the forms, reports, modules, etc. Each user gets their own copy of
the frontend; you would make design changes in your copy of the frontend
(opened exclusively). When you're satisfied with the design, you can either
give a copy of the new frontend mdb file to each user, or (better) create a
MDE file and distribute that.

See http://www.granite.ab.ca/access/splitapp.htm for a thorough discussion.
 
Back
Top