"This database has been opened read-only." Message and Fix Maybe?

[padlocked17]

All,

I'm getting the following message in Access and it's causing all kinds of headaches for the user. Any ideas why it's appearing and how to get rid of it?

Thanks,

 

[Uncle Gizmo]

My guess is the actual *.mdb file, or seeing as it looks like access 2007 the extension may be different,

My guess is that you need to open the actual file with explorer and have a look at the "read only" attribute.

 

[padlocked17]

That was my thought as well. But it's only occurring for one out of 8 users. The back-end data is fine and it's openeing a acclb file when the FE is opened. Users on this network don't have write access to their c: drives which is where the FE resides but that's the case for everyone. Why would this be affecting just one user if all systems are set up in the same manner?

 

[shirkb]

I don't have an answer; just basically the same problem. I have 5 XP machines networked with a MS 2003 file on one of them. I can open the file from any of the machines. I just added 6th machine with same OS and Access version but when I try and open the MS 2003 file across the network from this machine I get a message indicating that it is "read only"

 

[shirkb]

I am replying to my own post. The information I received was incorrrect. All the computers on the network were getting the Read Only message. The problem was found in the folder sharing properties on the server. Somehow the "Allow user to Read/Write files" box became unchecked.

 

[sps2]

Wow. Did anyone find a solustion to this problem? Beacuse for some reason that just happened here. We have several users at the server location that are not having a problem and all of our remote users that are getting this message. Everyone accesses the database from a network drive in this building but a lot of users are hundreds of miles away accessing the same network drive. Thoses users are getting the error. It has been working perfectly for years, this just started.

 

[mafhobb]

I am now seeing the same error

mafhobb

 

[Uncle Gizmo]

The solution was posted by "Shirkb"

Extract:
The problem was found in the folder sharing properties on the server. Somehow the "Allow user to Read/Write files" box became unchecked.