file already in use

[Guest]

I just setup my secured, split database back end on our server for
multi-users. Now when others try to open it they receive the message "File
already in use." which refers to the back end.

How do I troubleshoot this?

Thanks!

 

[Rick B]

Do the users have full access to that folder on your server? They have to
be able to read, write, modify, and delete in that folder so they can
properly update, create, and delete the locking file. If the database is
not in use, the first user in it creates the locking file. If it is in use,
each subsequent user updates that locking file. The last user to close the
database deletes that locking file.

 

[Rick B]

Please note, I was talking about Windows Permissions, not MS Access Security
settings. The System Administrator has to make sure the users have full
Windows Permissions.

 

[Wayne Morgan]

The file needs to be opened in shared mode. Go to Tools|Options|Advanced
tab. Set the "Default open mode" to "Shared" and, unless you know you have a
need otherwise, set "Default record locking" to "No locks". Do this for each
computer that will be accessing the database. Also, if you're opening the
database using a shortcut with a command line, make sure that you do NOT
have the /excl switch in the command line. This will force the file to be
opened exclusively. Once you've done that, with the database closed on each
computer check the folder that the back-end file is in and see if there is
an ldb file with the same name (before the period) as the back-end file. If
so, delete it. The users will need delete permission on the share and folder
that the file is in so that Access can delete the ldb file when the last
user closes the database.

If your mdw file is in the same folder as either the front-end or back-end,
make sure the mdw file does not have the same name as the other file it is
with. As stated above, an ldb file will be created with the same name as the
database file. This is true for the mdw file also, so if it has the same
name as the file it is with, both will try to create an ldb file using the
same name.

Example:
MyDatabase_be.mdb and MyDatabase.mdw will create 2 ldb files names
MyDatabase_be.ldb and MyDatabase.ldb. If the mdb and mdw file were both
called MyDatabase.*, then there would be a conflict when they try to create
their associated ldb files.

 

[Guest]

Thanks, Wayne! I ran through all of your direction and assured everything
except the delete permission of the database folder.

I'll have to address this with our computer people. If users have delete
access then won't they be able to access the folder and delete the database
file?

 

[Guest]

Thanks, Rick!

The folder with the database is supposed to be read-only for everyone and
only myself with delete permission. I'm in the process of verifying this with
our computer people because my manager has no problems accessing the
database. However, he's using WindowsXP with a higher version of MS Office.

This is raising more questions.

 

[Guest]

I'm a little confused by what you mean regarding "Windows Permissions." Could
you please clarify?

Thanks!

 

[Wayne Morgan]

Unfortunately, yes. One option to help is to make the share a hidden share
so that they can't just browse to it. Also, if the file is in use, it ought
to be locked and not deleteable. You will also want to keep a good backup of
the file, but you should do that anyway (files have been known to get
corrupted).

 

[Guest]

I just reviewed this with our computer people and the folder was setup as
read-only with only change access for several select people. I had this setup
but it was a couple years ago and I'd forgotten. This explains why my manager
could access the database as he's on the list of change access users.

I'm in the process of creating a new folder with full permissions for
everyone. Won't this allow anyone to delete the database file, too?

 

[Guest]

Thanks a bunch!

--
www.Marzetti.com

Unfortunately, yes. One option to help is to make the share a hidden share
so that they can't just browse to it. Also, if the file is in use, it ought
to be locked and not deleteable. You will also want to keep a good backup of
the file, but you should do that anyway (files have been known to get
corrupted).

 

[Wayne Morgan]

It will depend on the operation system being used on the computer where the
back-end file is located. If it is a Windows NT version (this includes
Windows 2k, XP, 2003 server) there are 2 types of permissions. The first one
is Share permissions. You set these on the share when you set it up. The
second type is NTFS permissions. These require the drive to be formatted
with the NTFS file system and they are similar to share permissions.
However, the NTFS permissions will work whether you go to the folder via a
network share or if you're on the computer itself. You need to make sure
that (as a minimum) you have Change permissions allowed in both the Share
and NTFS permissions for the location of the file.

 

[Rick B]

Sounds like you already understand. The permissions set on the folder by
the System Administrator.

Like I said, they need full access to the folder.

Yes, they would be able to delete the file. You should make backups
regularly.