Hi Nick,
If someone else is using the database at the moment, then Windows Explorer
will not allow you to delete the .LDB files. There's nothing wrong with
trying to delete them.
Without already having the code present to execute, which would kick other
users out of the database, the answer is no. You can use the App User utility
available here to try to identify all current users, and then ask each of
them to quit using the application:
http://www.mvps.org/access/modules/mdl0055.htm
Tom
______________________________________
:
Right at this moment I do have a couple .ldb files in the folder with the
database as you describe. Assuming this means that someone else is using the
database at this moment, is there any way to make changes or kick them out to
be able to make changes?
______________________________________
:
Hi Nick,
You didn't say whether this is a single-user database, or a shared
multi-user database. You are correct that the database must be opened
exclusively in order to make design changes. There is a possibility that a
locking database file remains in the same folder, when you close your Access
application and no one else has it open. If so, attempt to delete it. If you
are viewing icons in Windows Explorer, this file will have a lock icon.
Switch to a detail view, and you should see that the file is about 1 KB in
size. If all users are out of a database, the .LDB file should be deleted
automatically. It is not deleted if:
1.) A user does not have delete privleges
2.) A user crashed out of Access (power failure, Ctrl-Alt-Del, etc.) or
3.) The database is starting to become corrupt.
A shared mult-user database should most definately, without any question, be
split into front-end (FE) and back-end (BE) databases. The FE database
contains all queries, forms, reports, macros, modules, and shortcuts to data
access pages. It also contains any local tables that are used to store user
preferences, or to store fairly stagnant data (doesn't change very often),
such as a list of states. Each user should have their own copy of the FE
database saved on their hard drive.
The BE database is saved to a folder on a file server. It includes only
tables with the shared data. Each user must have RWCD privleges for the
folder, although different privleges can be set for the actual .mdb file.
In this setup, you should be able to change your copy of the FE anytime you
wish. If you need to make schema changes to the BE database then, yes, you
will ieither need to kick everyone out or wait until everyone is finished.
Tom
_________________________________________
:
In order to make changes to my database, I assume I need to open the database
"Exclusively". When I try to do this, I get the message telling me that I
don't have exclusive use of the database and therefore won't be able to save
my changes. What is the best way, if possible, to make changes to my
database while it is in use. Could I make the changes in a copy and then
copy the copy on top of my existing database? Do I have to wait till the wee
hours of the morning when it is not in use? I am the owner of all objects
and have "Open Exclusive" rights.
Nick
