Further to the comments by rpeare and Ajax, I'm going to suggest a few other things.
With database, get your tables normalized as has been suggested.
Also, for your use and for communicating with others trying to help you, get a clear statement of WHAT you are trying to do. Once you get to Access and tables you have jumped into HOW you have chosen to do something. But we don't know you. We don't know your environment. We have no idea what you business is, nor how it operates. So, to help us help you,tell us the 30,000 foot overview of your business to give readers some context; and to provide you with a written statement (for reference) of what you are trying to do.
Once readers understand WHAT you are trying to do, more focused suggestions and alternatives will follow. There may be many options for HOW to accomplish WHAT you are trying to do, but until we know WHAT it's hard to suggest How.
For reference and for experiencing table and database design, work through this tutorial from RogersAccessLibrary. You will learn about tables, fields, relationships by means of a process that can be used to design any database. You have to work through it, but you will learn concepts that will serve you well for a long time.
Before going too much further, there are links here that will help you.
Good luck.