I'm setting the AllowAdditions, AllowEdits and AllowDeletions properties of a form to False in the form's Activate event procedure. This effectively keeps the form read-only, except in one case: when I use a command button on that form to launch a second form (which is modal) and the second form modifies a text box value on the first form, when I close the second form and the focus returns to the first form, that same text box can now be further edited by the user, even though the form's AllowEdits property remains False. What's causing this, and how can I get around it? This is part of a project to develop an alternative to Access's own security system, and the first form's Allow... properties are set according to the current user's access rights, which are maintained in a Users table. Thanks for any help or suggestions.

Your form recordsource is not a table or updatable query. Or the recordsource is used by another form or query while your form is open.

The form's recordsource IS being used by the second form. Since my original posting, I think I've found a workaround - if I reset the form's Dirty property, it once again makes the form read-only, even after one of its fields has been modified by the second form.