I can make no sense out of the structure or target example you posted. What I think you should do is review normalization and naming conventions (3-1 is a poor identifier and you should not have parentheses in names) and then post back with a narrative on what the business entails if the suggestions don't help you with design. Often, starting out with what you have leads down some path that should be avoided because it's not properly designed. Not saying for sure that is the case here, but I suspect as much.
http://rogersaccessblog.blogspot.ca/...on-part-i.html
and/or
http://holowczak.com/database-normalization/
One source about how to name things - http://access.mvps.org/access/general/gen0012.htm
What not to use in names - http://allenbrowne.com/AppIssueBadWord.html
About Auto Numbers
- http://www.utteraccess.com/wiki/Autonumbers
- 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
The more we hear silence, the more we begin to think about our value in this universe.
Paraphrase of Professor Brian Cox.