Subform Data Entry Yes switches to No when navigating records in main form

[ljburton]

Before I start, thanks to everyone who posts – I’m new to Access 2016 and I’ve found almost every answer I’ve needed here

I’m capturing research about personal lubricants – manufacturers, formulas, ingredients, etc. Right now, I’m working on the forms related to manufacturers.

• I have a main frmManufacturers bound to tblManufacturers
• I store URLs, emails, phone numbers, and social links in their own respective tables.

Using email as an example, I have two subforms:

• frmEmailQry is bound to a query and is meant to display, edit, delete exiting records.
• frmEmailAdd is bound to the email table and is for adding new records. For this reason, I have set Data Entry = Yes.

When I first open frmManufacturer, the frmEmailAdd subform behaves the way I expect – new/blank record waiting for data.

But as soon as I navigate to another record in frmManufacturer, the frmEmailAdd subform changes from Data Entry = Yes to Data Entry = No. The subform shows an existing record, and not new/blank.

I’ve gotten this same idea to work in practice databases and I just can’t find the problem. Any help would be most appreciated

Thanks!
- Lisa

 

[bob fitz]

I think your subform is corrupt. Fortunately, it's a very simple form so won't take you long to re-create it. Alternatively, you could delete it and import it from an earlier backup.

 

[ljburton]

Hey Bob - Thanks for the quick reply.

I suspected corruption somewhere and had rebuilt the forms plus a bunch of other troubleshooting before posting.

Since the same issue was happening on 4 similar subforms, I thought something else might be corrupted and I just couldn't find it.

I decided to import the tables into a new db and to rebuild the queries and forms. In the process, I found the problem ... not corruption - user error!

In case you're interested ... Using email as an example

frmEmailAdd uses a combo box to get tblContactType ID and store it in tblEmail as a foreign key.

Problem was, I had it set to store txtContactType instead of IDContactType as the fk.

Thanks again!

 

[bob fitz]

Hey Bob - Thanks for the quick reply.

I suspected corruption somewhere and had rebuilt the forms plus a bunch of other troubleshooting before posting.

Since the same issue was happening on 4 similar subforms, I thought something else might be corrupted and I just couldn't find it.

I decided to import the tables into a new db and to rebuild the queries and forms. In the process, I found the problem ... not corruption - user error!

In case you're interested ... Using email as an example

frmEmailAdd uses a combo box to get tblContactType ID and store it in tblEmail as a foreign key.

Problem was, I had it set to store txtContactType instead of IDContactType as the fk.

Thanks again!

Glad you got it sorted out and thanks for posting back with what you did to fix it.