Link to home
Start Free TrialLog in
Avatar of Dennis Hicks
Dennis HicksFlag for United States of America

asked on

Cannot open vital database!

Hello,

I have a serious situation with Access 2016. We have a database here at work that will not allow a form to be opened. The first message received upon the main form opening is that the database is in read-only mode, which it should not be. So when trying to open the main data entry form, the message displays that the OpenForm action was canceled. This is our Inventory database and is vital to our daily operations, so I could really use some help here. This happened spontaneously and no modifications have been made to any part of the database. Also, for some reason, this has affected ALL backup copies of the database, some going back to last year. Can someone please offer some advice as to how this can be fixed, and possibly an explanation as to how this could have happened in the first place??? Thank you.
ASKER CERTIFIED SOLUTION
Avatar of Anders Ebro (Microsoft MVP)
Anders Ebro (Microsoft MVP)
Flag of Denmark image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Do you have a backup? Can you make a copy of the actual file without an error message?
Avatar of Dennis Hicks

ASKER

I tried that but it didn't help. We have multiple backup copies of this database, and they have all become affected by this issue. When I open the DB and get the message that it is read-only, it says in order to edit I need to make a copy of the DB. So I do a Save As, but I still get the OpenForm message on the newly saved copy.
Anders, the permissions are fine. This is affecting multiple users. Our network team is trying to find a resolution, but we have been down over 24 hours now.
Yup, that sounds like a file permission error as per the first comment
You must have READ/Write access to both the frontend folder and the backend folder. If this issue also affects the backups, it sounds like the issue is with the backend file.
Sorry, it turns out that permissions were accidentally modified without my knowledge. Sorry for the inconvenience. Thanks!
@Dennis: Don't sweat it. It's no inconvenience. That is what sites like this is for. Asking a question, presenting a problem and its symptoms, and benefit from the experience of others.

Why do you think I could "guess" that it was a permissions issue? Because I've BEEN there.

Have a nice day (and remember to close the question)
Pardon my ignorance, but how do I close the question?