Database changes to Read-Only!

[TessB]

Decided to create a new topic as my post to another seems to get buried quickly by brand new posts. (I know I usually look for replies = 0 if I'm looking to help someone) So forgive the double post please.

I need a crying smilie!

Issue:
Built a database which one user with Full Version Access has been using successfully for a week or so. RunTime Access was installed on other users PCs and a shortcut to the database placed on their desktops.

The database is on the network, not an SQL server. On Friday, I found the database had turned into a Read-Only database. I knew from this and other posts that this can happen if the users do not have Write and Delete rights to the drive.


I couldn't delete the database, or rename it, so it's still out there. I made a copy and went around to everyone (about 12 users) and gave them a new shortcut.

I tested everyone's PC to make sure that when the database was accessed, the .ldb file was created and deleted when the database was exited.

The user with full version of Access worked with the database until lunchtime and then exited when she went to lunch. When she came back, the new copy of the database had reverted to Read-Only. I am at a loss! The database will be a vital part of their job procedures. Where else should I begin to troubleshoot? How can I make sure this will not happen again?

Thanks for your time
Tess

 

[Ron_dK]

Have you checked the attributes settings in the database properties.

I had a sort of similar problem the other day and it appeared that
the network admin had changed some of the permissions.

You might verify the settings as given in the dbase itself
( File/database properties ) or right click the dbase properties at the appropriate netwerk location .

Hope this helps,

Cheers , Ron

 

[TessB]

Thank you, Ron for taking time to respond.

The database properties do not show that it is read only. Also, last night, when almost everyone had gone home, I decided to check the database again to see if it had reverted to normal. It had. This has happened to another database on the network before. I am sure it has something to do with either the way people are exiting the database improperly somehow, or their network permissions. But, as I said, I tested each PC to make sure they could both add and delete things from that network folder.

Any other suggestions? I can't be the only one who has ever experienced this horror.

 

[Pat Hartman]

Tess (and others), if you're having trouble finding threads that you created here's two solutions:
1. subscribe to them. That way you'll get an email whenever anyone responds. I don't recommend subscribing to every thread you post to, you're email will be flodded.
2. Under any of your posts, click the search button. You should see your posts in descending date order.

 

[Ron_dK]

Tess,

I was just thinking : Isn't there any (hidden) module in your Dbase which toggles the read-only status while exiting the
dbase.

 

[TessB]

No, I built the thing from scratch and know every nook and cranny in it. No such thing. And it's happened on another database I've built as well, so it is not specific to only one database. The one thing in common is that both databases are being used by people with RunTime Access.

 

[gaganji]

Same problem

Hi Tess,

I know this is three years later but I'm wondering if you found a solution to this problem you were facing. I seem to be facing the same issues.

Thanks a lot!

 

[Jakboi]

I am having the same issue as well...

 

[The_Doc_Man]

Here is one possible issue:

The shared database was not properly secured such that one user is coming in early with OpenExclusive. While open in that mode, it is read-only to all except the one who got there first. When that user leaves, the database reverts to read/write.

The database workgroup file is the culprit. If the database were properly secured, the above situation could never happen. Search the forum for threads on securing a database via workgroups. There must be a gazillion such posts. Well... ok, maybe not quite that many. But a lot.

 

[gertv7]

Hello,

I have the same problem. I also think that the ms access database turns into read-only after the (windows) defragmentation of the hard disk.

Could the defragmentation be the source of the problem?