Sub-form does not allow edits

[WCStarks]

Even though all allows are yes and record lock is no, this sub-form, which used to allow edits, no longer does. I can edit the table directly, but not through this form. See attachment. Is there some other permission I don't know about?

[davegri]

Make Data Entry = No
The Yes setting will allow a form to only add new records, no viewing or editing old records.

[Welshgasman]

Data Entry = No

The most misnamed setting in Access

[WCStarks]

Make Data Entry = No
The Yes setting will allow a form to only add new records, no viewing or editing old records.

Thanks both of you. I changed the Data Entry property to "No" on the sub-form. So doing, while the sub-form is not in context with its parent form, I can now edit all the records. However, when I attempt to edit in the sub-form while it is in context with its parent form, it no longer allows editing. So, we are partway there. What else could be going on? I can edit in the parent form.

[WCStarks]

Even though I was able to edit in the parent form, I thought I would look at its properties. I found that the Additions, Deletions and Edits properties were set to "No." I changed them to "Yes," and then tried to edit the sub-form in context. I found that I can now edit in the sub-form. So, the issue is resolved.

It is curious that I was still able to modify records in the parent form, even when those properties were set to "No".

[June7]

That is odd because Edit No should not allow any editing to existing data in controls.

[WCStarks]

That is odd because Edit No should not allow any editing to existing data in controls.

If you look at the image I posted with my original query, you will see that the parent "Members" form is subordinate to the "Manage SCATeam" navigation form. I looked in the "Manage SCATeam" form and found that the Data Entry property is set to "No" and the several allows were all set to yes. So, it would seem that the settings for the parent form overrides the settings of its sub-form. This really is strange and unintuitive behavior.

The original "Data Entry" setting for the top two was "no" and for the bottom form was "yes." The allow settings of the nested forms were as listed below, with the associated functionality:

Top form: Data Entry= No, Allows = yes
Subform: Data Entry = No, Allows = no (it can edit)
Subform: Data Entry = Yes/No, Allows = yes/no (it cannot edit)

Top form: Data Entry = No, Allows = yes
Subform: Data Entry = No, Allows = yes/no (it can edit); When allows = yes, the subform can edit.
Subform: Data Entry = Yes/No, Allows= yes/No (it can edit)

[Missinglinq]

Yes, it seems non-intuitive...and Data Entry is, indeed, one of the most odd names in Access (but only one of a number of odd names,) considering what it does (or doesn't do) but what you have to remember, to understand this, is that a Subform is a Control on the Form above it in the hierarchy. If Edits = No/False on the Main Form, the Subform Control on that Main Form cannot be 'edited,' which is how the Access Gnomes look at it!

Linq ;0)>