PDSWSS
asked on
Why is our Access DB indicating "Read Only?"
We are running an MS Access 2000 DB off a shared drive on our server (Front End and 2 Backends).
The database has been running very well. I just mapped another computer to the Shared drive and the same users who can Read/Write etc from other computers are getting "Read Only" message from this computer. Any ideas why this would specific to one computer?
The database has been running very well. I just mapped another computer to the Shared drive and the same users who can Read/Write etc from other computers are getting "Read Only" message from this computer. Any ideas why this would specific to one computer?
Emil_Gray
Right click on the unopened database and find the properties for the file. You probably will see the Read Only block checked. Uncheck this box.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Check default Access settings for this new computer. May be it opens DB in exclusive mode?
Try to set this option to "Shared"
Try to set this option to "Shared"
Along the lines of what Ramanhp suggests:
The folder hosting your Backend database must be configured so that all users have at LEAST Modify permissions on that Folder. Users must be able to read, write, create and destroy items in that Folder. This is so Access can work with the locking file (the .ldb file) it uses to manage user interaction, logins, etc.
The folder hosting your Backend database must be configured so that all users have at LEAST Modify permissions on that Folder. Users must be able to read, write, create and destroy items in that Folder. This is so Access can work with the locking file (the .ldb file) it uses to manage user interaction, logins, etc.
You may also check the shared folder's security/user permission where the database is being stored.
nlhizon: Was there some reason you basically repeated the same post I made several hours earlier?
"I just mapped another computer to the Shared drive"
My suggestion is to not use 'mapped drive letters', but instead use the Full UNC path to the Back Ends on the shared drive.
mx
My suggestion is to not use 'mapped drive letters', but instead use the Full UNC path to the Back Ends on the shared drive.
mx
ASKER
I will try some of these solutions as soon as I have time.
Please remember in providing these solutions that the permissions on the DBs must be OK since the same user could open the DBs with read/write permissions on one computer
but not on another computer. The problem must be computer specific and not due to permissions each database. I had already confirmed that the user had read/write permissions.
Thanks
Please remember in providing these solutions that the permissions on the DBs must be OK since the same user could open the DBs with read/write permissions on one computer
but not on another computer. The problem must be computer specific and not due to permissions each database. I had already confirmed that the user had read/write permissions.
Thanks
ASKER
I solved the issue by putting the user in an AD security group that had the correct permissions.
However, the user already had the correct permissions but would get the READ only message before I put their account into the group I mentioned.
Not clear why this is the case. Any ideas?
Not clear if any of the expert solutions are relevant to this solution.
However, the user already had the correct permissions but would get the READ only message before I put their account into the group I mentioned.
Not clear why this is the case. Any ideas?
Not clear if any of the expert solutions are relevant to this solution.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.