A sideline question, generated because of the knowledge demonstrated in your reply above.1. Your schema is not properly normalized. Any time you add a numeric suffix, you should know that you have a 1-many relationship and the many-side data should reside in a separate table. You have PNA_1- PNA_22 with a couple of a's as well as PQ's, If PQ and PNA go together, they can both be in the same table.
2. The visit table is NOT needed in any of the subform queries. the Master/Child link is providing the Foreign Key when the record is saved.
3. The perioperative data table is bound to three subforms. You are probably getting three records because the main form is set to data entry and so as you move from form to form, Access is making sure you have a "new" record. I would fix the design issue with this table. Add a "group" to the table so you can have three groups of data. That way each form can be bound to the same table but each question ends up in a separate row. You will have to populate the "group" in the subform's BeforeUpdate event.
You can verify that the duplication is being caused by the visit form being opened as data entry. Just temporarily change the Switchboard Items table to test.
I just tried removing the unnecessary joins as well as changing the way the form is opened and neither solve the duplication. Fix the table design issue and move on.
Is there an MS-Access set of classes from someone you'd either recommend, or at least have good things to say about?
I'm having to build some tools to get things out of paper where I am at, and scraping the rust off old skills. Used to be a programmer/analyst many years ago. Probably the best way to do that is to refresh with current online coursework and exercises.
Thanks in advance.