You really need to read up on database normalization. You took the advice to heart but then showed a spreadsheet design for the observations table. Spreadsheet format (wide and not tall) is not suitable for databases. Plus there is no way that the ID would be in the same table 3x so the relationship is invalid, sorry to say. Maybe read up and make sure you understand normalization, but I strongly suggest you study naming as well. Some fairly bad examples there
Might as well give you the whole enchilada...
Normalization Parts I, II, III, IV, and V
http://rogersaccessblog.blogspot.com...on-part-i.html
and/or
http://holowczak.com/database-normalization/
Entity-Relationship Diagramming: Part I, II, III and IV
http://rogersaccessblog.blogspot.com...ng-part-i.html
How do I Create an Application in Microsoft Access?
http://rogersaccessblog.blogspot.com...cation-in.html
Important for success:
Naming conventions - http://access.mvps.org/access/general/gen0012.htm
https://www.access-programmers.co.uk...d.php?t=225837
What not to use in names - http://allenbrowne.com/AppIssueBadWord.html
About Auto Numbers
- http://access.mvps.org/access/general/gen0025.htm
The evils of lookup fields - http://access.mvps.org/access/lookupfields.htm
Table and PK design tips - http://www.fmsinc.com/free/newtips/primarykey.asp
About calculated table fields - http://allenbrowne.com/casu-14.html
About Multi Value Fields -http://www.mendipdatasystems.co.uk/multivalued-fields/4594468763
The more we hear silence, the more we begin to think about our value in this universe.
Paraphrase of Professor Brian Cox.