Should I create a new table for each Run?
Absolutely not. The 1st thing you need to do when designing a db is forget what you know about Excel as it doesn't relate at all. Sheet is column based, db is row based. Rows of one table are "related" to rows in another (hence relational database) by common or related data. This is very basic stuff and quite involved and really is beyond the scope of a forum like this. Maybe someone will think differently on that.
Introductory books and/or web tutorials are when you need to start - if this is warranted. Sometimes a spreadsheet is the right tool.
Here's all the introductory stuff I have. Ignore any of it at your own risk
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.ca/...ng-part-i.html
How do I Create an Application in Microsoft Access?
http://rogersaccessblog.blogspot.ca/...cation-in.html
Important for success:
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
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.