Why are my fields protected?

[Jerry McNabb]

I have built an Access database that has as its primary table tblAlumnus. The
form frmPersonal is used to add and edit the record. It provides a command
button to link to the form frmContact to maintain the contact information;
however, in frmContact, all the fields are protected. The form properties are
set as follows:
Recordset Type = Dynaset,
Allow Edits = Yes,
Allow Deletions = Yes,
Allow Additions = Yes,
Data Entry = No, and
Record Locks = No Locks.
I have tried opening frmContact without frmPersonal and by using frmPersonal
and then closing frmPersonal after I am in frmContact, but neither unprotects
the fields.
Why?

 

[Douglas J. Steele]

What do you mean by "protected"? Are you getting a message that the data
isn't updatable? What's the recordsource of the form? Is it updatable?

If you're not getting a message that the data isn't updatable, what are you
experiencing?

 

[Jerry McNabb]

What do you mean by "protected"? Are you getting a message that the data
isn't updatable? What's the recordsource of the form? Is it updatable?

If you're not getting a message that the data isn't updatable, what are you
experiencing?

 

[Jerry McNabb]

Everytime I try to key into one of the controls an alarm rings, and the data
does not change on the screen. The recordsource is tblAlumnus. It is
updatable.

 

[Douglas J. Steele]

If you open the table directly, rather than go through the form, are you
able to make changes to the data?

 

[Jerry McNabb]

Yes I am.

If you open the table directly, rather than go through the form, are you
able to make changes to the data?

 

[Rick Brandt]

Yes I am.

Did you use the form wizard? Many users assume that because those chose a table
with the wizard that this means the form is bound directly to the table. Often
that is not the case. Your form could very well be based on a SQL Statement
against your table and not the table directly. You have to look at the
RecordSource property of the form to confirm what you have.

 

[Jerry McNabb]

I built the form through a wizard. When I look at the form properties, it
starts with "Select tblAlumnus..." When I click on the build button <...>, it
takes me to an SQL statement.

 

[Douglas J. Steele]

If you run that SQL, is the resultant recordset updatable?

 

[Rick Brandt]

I built the form through a wizard. When I look at the form properties, it
starts with "Select tblAlumnus..." When I click on the build button <...>, it
takes me to an SQL statement.

Well there you go. Your form is bound to a query, not a table. Not all queries
allow editing though often one that does not can be modified so it will allow
edits. Post the full SQL Statement and someone might be able to suggest changes
that will solve the problem.

 

[jahoobob via AccessMonster.com]

Sometimes changing the Recordset type to Dynaset (Inconsistent Updates)
"fixes" this problem.

I built the form through a wizard. When I look at the form properties, it
[quoted text clipped - 6 lines]

against your table and not the table directly. You have to look at the
RecordSource property of the form to confirm what you have.

 

[Jerry McNabb]

I changed the Record Source Property to "Select tblAlumnus" and the fields
were updatable. However the one field from another table was displayed as
"#NAME?". So I created a query and everything worked.

Thanks very much.

 

[smart]

I have built an Access database that has as its primary table tblAlumnus.
The
form frmPersonal is used to add and edit the record. It provides a command
button to link to the form frmContact to maintain the contact information;
however, in frmContact, all the fields are protected. The form properties
are
set as follows:
Recordset Type = Dynaset,
Allow Edits = Yes,
Allow Deletions = Yes,
Allow Additions = Yes,
Data Entry = No, and
Record Locks = No Locks.
I have tried opening frmContact without frmPersonal and by using
frmPersonal
and then closing frmPersonal after I am in frmContact, but neither
unprotects
the fields.
Why?