Please add another System checkbox to set another behavior: If checked, and when a DB is opened read-only either explicitly or by default, then when it's locked, it should revert back to read-only. If we've chosen read-only by default, there's no reason to stay read-write when locked, right? Altho at that point, we probably also want the "Open as read-only" checkbox on the unlock dialog. Essentially unlocking becomes nearly identical to opening.
We do love the read-only feature! It helps this work in our environment. But someone will change to R-W to add or edit, and then forget they have. Later, often much later, someone else will want to add or edit, and we get the dreaded message that we cannot change to R-W, and have to go find someone, or kill their process. This is what we came up with for a solution.