By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
429,101 Members | 1,340 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 429,101 IT Pros & Developers. It's quick & easy.

Locked out

P: n/a
Hi,

We have been using access for some time to write school reports. What I
have written is pretty amateurish, but it does the job! Recently it has
been falling over an I don't know where to start in locating the problem.
It tells one user that the database is being used exclusively by another
user. When this user comes out, it then says it has been left in a state
where it needs repairing. Usually, it can them be repaired, but sometimes
it even then that it cannot be repaired because it is being used. I can
copy and repair it then, but then acn't even delete the orignal. All I can
do is lock it and hide it and save the new one with a slightly different
name so staff can go on using it.

Any ideas would be appreciated.

Thanks in advance
Nov 13 '05 #1
Share this Question
Share on Google+
3 Replies


P: n/a
JohnM wrote:
Hi,

We have been using access for some time to write school reports. What I
have written is pretty amateurish, but it does the job! Recently it has
been falling over an I don't know where to start in locating the problem.
It tells one user that the database is being used exclusively by another
user. When this user comes out, it then says it has been left in a state
where it needs repairing. Usually, it can them be repaired, but sometimes
it even then that it cannot be repaired because it is being used. I can
copy and repair it then, but then acn't even delete the orignal. All I can
do is lock it and hide it and save the new one with a slightly different
name so staff can go on using it.

Any ideas would be appreciated.

Thanks in advance

Maybe you need to check the shortcuts on the desktop for all users that
open this database or MSAccess. See if anyone has a /excl in the
command line in the shortcut. If a person has /excl in it, a message
box will inform that operator that the database can't be opened
exclusively but it will open. However, if that person is the first one
in, then other users will not be able to get into it.

Get onto google groups http://groups.google.com, advanced search,
(*Access* for the group) and look for a utility/function to determine
which users are in the system. There was a program for A97 called
LDBView.Exe. There is another one for A2000 onward. Look for topics
along the lines of "view users in application", "view users in
database", etc

The file that appears to be causing the problem is your LDB file. This
fild contacts the locks and users. When all users exit the app, this
ldb file should disappear. As long as one user is in the system, you
will have an LDB file for the database name. You might want to try to
delete it if it exists and you know everybody is out of the app.
Nov 13 '05 #2

P: n/a
From your diescription, I think you have multiple users logging in to the
same front-end or monolithic database. Doing so greatly increases your risk
of database corruption, which seems to be at least one of your problems.

You should split the Tables and Relationships (which will now be called the
"Back End") from the Queries, Forms, Reports, Macros, and Modules (which
will now be called the "Front End"). Give each user a copy of the Front End,
and link the tables in the back end, using the Linked Table Manager or code
that you include.

For other good suggestions on performance and on avoiding corruption, visit
MVP Tony Toews site http://www.granite.ab.ca/accsmstr.htm. It is the best
collection of links and information about using Access in a multiuser
environment that I know about.

Oh, and don't disregard Salad's suggestions.

Larry Linson
Microsoft Access MVP
"JohnM" <jo**@jmawer.demon.co.uk> wrote in message
news:d9*******************@news.demon.co.uk...
Hi,

We have been using access for some time to write school reports. What I
have written is pretty amateurish, but it does the job! Recently it has
been falling over an I don't know where to start in locating the problem.
It tells one user that the database is being used exclusively by another
user. When this user comes out, it then says it has been left in a state
where it needs repairing. Usually, it can them be repaired, but sometimes
it even then that it cannot be repaired because it is being used. I can
copy and repair it then, but then acn't even delete the orignal. All I can do is lock it and hide it and save the new one with a slightly different
name so staff can go on using it.

Any ideas would be appreciated.

Thanks in advance

Nov 13 '05 #3

P: n/a
"JohnM" <jo**@jmawer.demon.co.uk> wrote in message
news:d9*******************@news.demon.co.uk...


We have been using access for some time to write school reports. What I
have written is pretty amateurish, but it does the job! Recently it has
been falling over an I don't know where to start in locating the problem.
It tells one user that the database is being used exclusively by another
user. When this user comes out, it then says it has been left in a state
where it needs repairing. Usually, it can them be repaired, but sometimes
it even then that it cannot be repaired because it is being used. I can
copy and repair it then, but then acn't even delete the orignal. All I
can
do is lock it and hide it and save the new one with a slightly different
name so staff can go on using it.

You can't really fault-find on a production file, ie one that is in use.
Further, you should not share an mdb file, you should split it into a front
and back end and give each user their own copy of the front end (back end =
all data tables, front end = everything except native tables but with linked
tables to the back end).

With the FE/BE configuration, each user gets their own FE linked to the BE.
You have a development copy of the FE which you can deliver to each user
after you make a change. You can also compact/repair etc to your heart's
content because no one but yourself will have access to the development
copy.

Search this group and the on-line help for "split database" if you need more
info.

Good luck.

Keith.
www.keithwilby.com
Nov 13 '05 #4

This discussion thread is closed

Replies have been disabled for this discussion.