Improve company productivity with a Business Account.Sign Up

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 540
  • Last Modified:

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?
0
PDSWSS
Asked:
PDSWSS
  • 3
  • 2
  • 2
  • +4
3 Solutions
 
Emil_GrayCommented:
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.
0
 
RamanhpCommented:
there seems that one instance of the database is opened in background , manually  or through the script.

the connection to the database first needs to be closed and then u may open it again.

the other reason could be having NO WRITE access of the folder to the USER accessing it.
well in this case, please grant a write access to the user first
0
 
als315Commented:
Check default Access settings for this new computer. May be it opens DB in exclusive mode?
Try to set this option to "Shared"
0
What Kind of Coding Program is Right for You?

There are many ways to learn to code these days. From coding bootcamps like Flatiron School to online courses to totally free beginner resources. The best way to learn to code depends on many factors, but the most important one is you. See what course is best for you.

 
Scott McDaniel (Microsoft Access MVP - EE MVE )Infotrakker SoftwareCommented:
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.
0
 
nathanielIT ConsultantCommented:
You may also check the shared folder's security/user permission where the database is being stored.
0
 
Scott McDaniel (Microsoft Access MVP - EE MVE )Infotrakker SoftwareCommented:
nlhizon: Was there some reason you basically repeated the same post I made several hours earlier?
0
 
DatabaseMX (Joe Anderson - Microsoft Access MVP)Database ArchitectCommented:
"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
0
 
PDSWSSAuthor Commented:
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
0
 
PDSWSSAuthor Commented:
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.

0
 
als315Commented:
It is question to server group. You need allow network access and also add this user in Security tab:
http://technet.microsoft.com/en-us/library/cc773004(WS.10).aspx
0
 
Scott McDaniel (Microsoft Access MVP - EE MVE )Infotrakker SoftwareCommented:
Ramanhp and myself both suggested that you examine permissions and gave details of what permissions should be examined. Adding users to a different group (which would have given them different permissions) is more-or-less the same thing as changing permissions - two paths to the same endpoint.

If you review the two accounts, somewhere down that line you'll find a permission that is different, either in a Group that all users are assisgned to, in a Group Policy, or in permissions assigned to single users.

Whatever the case, permissions was at the root of this issue, as it always is.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Upgrade your Question Security!

Your question, your audience. Choose who sees your identity—and your question—with question security.

  • 3
  • 2
  • 2
  • +4
Tackle projects and never again get stuck behind a technical roadblock.
Join Now