There is no answer to that question if you're going to be concerned about normalization. Your design suffers from Excelitis i.e. designing like a spreadsheet. Your current plan is to have repeating fields to say the least and perhaps unrelated fields that belong in some other table. Hard to say more without knowing more about the purpose of the db. Best that you learn normalization and then come back because it is fundamental and crucial to success. I could post just links for normalization but I know that you could benefit from all of these if you care to do all the research. These can save you a lot of grief later on.
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 - https://www.isladogs.co.uk/multivalu...lds/index.html
The more we hear silence, the more we begin to think about our value in this universe.
Paraphrase of Professor Brian Cox.