Forum Discussion
Access Front-end Switches to Read-only
This happens with a single workstation, so it's related to how that workstation is configured. Is the same person using this workstation each time the problem recurs?
Perhaps there is unique software installed on it that is not on other computers in your network? You mention a check reader, for example. How about Anti-Virus software? Is that the same for all workstations?
Thanks for the quick reply.
Yes, same user.
Working with the unit this afternoon I learned that the FE folder permissions can be set to Read/write and it will revert to Read-only after a restart or complete shutdown. Then manually resetting the folder to Read/write doesn't release the lock on the FE.
Tomorrow morning, I will provide more details.
- One other long-shot occurred to me. How is the Front End accdb deployed to users? Do you have, for example, a process that replaces the FE on the user's computer each time they start?
I also should establish that we are not talking about Trusted Locations for the Access accdbs.
We are talking about permissions on the folders on the computer itself, correct?
That's not an Access problem, then. It's something to do with the way that folder is configured in Windows. Or with the user's Windows account. Moreover, apparently it's happening on the user's computer, which is even more puzzling.
It just occurred to me, though, that there is a contradiction in the way this problem was originally described.
"At random times, on only one workstation, the FE will not allow data edits. The folder and content within the folder will not be marked as Read-only."
...
"And the switch to read-only took place while the user was working in the app."
It is one way or the other, but it can't be be not marked as Read-only, and also be read-only, can it?
Perhaps you can clarify what that means.In any event, if the FE accdb is located in a folder on the user's local computer, and not somewhere on the network, and if the user's permissions on that folder can arbitrarily change from read-write to read-only, that's a problem far outside Access.
I'm still suspecting there's more to the story than you've discovered yet. And I also think your IT support, such as it is, needs to be more involved in resolving the problem.