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.