Read-only problem

[kjzele]

My supervisor is attempting to fix his multi-user database. It seems when I
open the access database he created, I can only open it in "read only."
Three others in my group can access this database and modify or edit
information as needed.

Each individual in my group has their own file they can open. (This must be
linked to the Admin database somehow.) For instance, databases for each of
us are named for the individual who uses them: KimNewLie.mdb,
AaronNewLie.mdb etc.


I need to disable the read only feature, so that I can make edits or changes
as needed.

Can anyone help me understand why I am the only one, (out of a group of 4)
that read only is only way I can open the database?

 

[kjzele]

Mike,
The attributes read only box is NOT checked, but archive is.
There are five front end users, but only three of them work. Two are read
only.
File permissions come from the parent and allow all users modify permissions.
The file originated as a 2003 database that was upgraded to 2007, which
crashed.
When it was restored two of the front end user files became read only.

 

[MikeJohnB]

The only other thing I can think of is Does He/She have full - read, write,
create and delete - privileges on the network

Try creating a folder in the same location as the MDB, does it allow you to
do that?

Just delete the folder if it does. But that will indicate if you have
permissions.

Its easy for IT to forget to click a couple of permission boxes when the set
up the system for different users.

Is there a *.LBD file present?

 

[MikeJohnB]

Sorry, I meant create a folder where the Back End not the front end.

 

[kjzele]

Thank you MikeJohnB:

My supervisor is trying EVERYTHING you suggested and then some. He now has
quite a few database files he is working with and I hope that doesn't get
confusing.

There is a *LBD file present. Does that mess with "read-only" access?

I will get back with you if we need further help.

 

[MikeJohnB]

The *.LDB file is a lock file indicating that someone is using the database,
sometimes they become orphaned when someone crashes out. if no one is using
the database, there should not be a *.ldb file present.