I was leaning towards not being a pest with too much detail
You are far, far away from that - still. Actually, what could limit responses is when getting the needed details is like pulling teeth.
Your table names are not that descriptive - unless they don't really represent your db, in which case, that's often another problem in posts (examples don't reflect reality). Since both the visited (are these patients? residents? inmates?) and the visitors likely have names, tblNames doesn't provide much info. Take another stab at explaining the "business" if you are looking for design advice. You say you're not new to Access, but I have to say I don't agree with your table designs. F'rinstance,
- visit data doesn't belong in Client records.
- actionID PK belongs in VisitsToClients.VisitAction as a FK, not the text value [VisitAction] from tblVisitAction - unless maybe you are going to employ table relationships with cascading updates.
- you name the same things differently from one table to another - will confuse you sooner or later
- frmVisitedNew will not work because it's missing one or more key fields. This suggests you designed the form before the query, or you didn't test the query first.
Respectfully, maybe you should research normalization, or at least ensure you understand Entity versus Attribute. You seem to have made some basic design errors.
Last edited by Micron; 06-11-2018 at 06:35 PM.
Reason: clarification
The more we hear silence, the more we begin to think about our value in this universe.
Paraphrase of Professor Brian Cox.