I have a database on a network which has no security setup; everyone who has rights to its directory has full rights to the application. From time to time, it becomes "Read Only" and no one can do anything that requires writing to the local tables (the back end database is "Read Only" for everyone.) Checking the database properties shows the database as not being "Read Only" and changing it to read only and back again does nothing.
So far, the only way I have been able to solve this problem is to replace the "Read Only" database with a backup copy that is not "Read Only".
Hi grnzbra (tho' Lord knows I'm probably teaching you to suck eggs)
I've had a similar problem:
Front end saying 'read only', but not always
No locked files visible, but unable to replace back end files when we update (daily at lunchtime)
Does it still display the 'read only' if it's only you in the dbase? If so, then I think you might have a permissions problem.
In an effort to correct it:
Are all users using same version of Windows & Access? Eg one machine hasn't been upgraded etc
Check that new user(s) doesn't have exactly the same permissions as others?
Change in server/network setup that you're unaware of
Dodgy network (always a standby!!)
The fix I used:
Import the forms, queries etc into a fresh new dbase (as I'd assumed some corruption). Didn't solve the problem (my problem turned out to be a permissions issue).
I then coded it so that the database (theoretically!) shut down if during update time. I've just added more code to shut down the database if inactive for 5 minutes as I'd discovered the dbase remained open if it had been opened before the update time. Ah, life's learning curves.
You're much more experienced than I, so have you tried recording who is in the database, so you can track to see when the dbase becomes read only (eg if Fred logs in first then it's read only, if Jo does then it's OK)?
Very painful & depending on the amount of users, get them to log in one at a time & see if it's OK.
I also refer to a reply to a post on this site dated June 2006 (locked files).
Code:
The mechanism is that an exclusive file-system lock is being taken out on the .MDB file because the person opening the file cannot open a .LDB file to hold the shared record-locking data. The only way that access to the .MDB can still happen is to grant exclusive access.
If you are the first user and lack the correct permissions, the file is locked exclusively for you. If you are NOT the first user, the file will be locked because you cannot take out an exclusive lock on the file - it is already locked by another person.
I'd be very surpised if I've solved the problem - but may have given you a clue
