Problem opening a database

J

joshroberts

I have a database that we've been using for a year now that has just recently
started having some problems when multiple users try to use it at the same
time. The error I get is:
"Could not use 'database name'; file already in use."

The first thing I did was doublecheck the security settings (which weren't
changed) ans everything appears normal. Also, I've noticed that the file
that pops up when someone is in the database "Access Record-Locking
Information", has stayed active even when I no that no one is in the
database. I fixed this problem by moving the file to a new folder (the
record locking file stayed in the old folder) but it popped up again the next
day. Is this a bug in Access and is there a fix? I'm using Access 2002.
 
S

storrboy

I have a database that we've been using for a year now that has just recently
started having some problems when multiple users try to use it at the same
time. The error I get is:
"Could not use 'database name'; file already in use."

The first thing I did was doublecheck the security settings (which weren't
changed) ans everything appears normal. Also, I've noticed that the file
that pops up when someone is in the database "Access Record-Locking
Information", has stayed active even when I no that no one is in the
database. I fixed this problem by moving the file to a new folder (the
record locking file stayed in the old folder) but it popped up again the next
day. Is this a bug in Access and is there a fix? I'm using Access 2002.
Click to expand...


By the sounds of it it's not a bug, but a matter breaking one of the
first rules of db sharing...Don't.
Split the db into a front-end (forms, reports, queries, code etc.) and
a back-end (tables).
The locking file is required by the db, so yes it's going to create a
new one if it dosen't see one.
 
D

Douglas J. Steele

When you say that you checked the security settings, which settings did you
check? You may need to look at both the security settings for the folder
itself, and for the share created so that others can use that folder.
 
J

joshroberts

This is the back end of the database. The problem is that when multiple
users draw from those tables at the same time it won't let them. Once again
this database has functioned well for a year and just recently developed this
problem. Also, I understand that the record locking file is required by the
database and that is not the problem. The problem is that it is creating one
that never goes away regardless of whether the database is in use.
 
J

joshroberts

I checked the settings in the database and they are set appropriately. Also,
this database is contained in a folder with two other databases that do not
have this problem.
 
Top