I want to use a relational database
I'd like to create a database that allows me to combine all of this information into a single table
Those 2 statements are at odds with each other. I went with the latter when suggesting Excel since it was posted after. I copied your table idea but considered that to be a main table I and thought some of the examples were progressions of the same table(s). Perhaps what I quoted was a junction table? That would be a different story. Not seeing a manager table kind of led me in that direction. RE:
I want to make a table for each manager
Don't do that. Maybe what is confusing you at this point is that notion. Based on my current (and perhaps flawed) understanding, you need
tblManagers
tblProducts
tblObjectives
IF objectives are linked to products AND 1 product can only have 1 objective AND only 1 manager is responsible for a product then
tblProducts can have
- tblObjectives.ObjectiveIDfk (could also put Objective field in tblProducts but less flexible)
- tblManagers.ManagerIDfk
So that's 3 tables. If multiple products can have multiple objectives (many to many) or if multiple managers are responsible for multiple products then you need junction tables instead.
As Minty said, the picture is not clear.
This is about as general as I can make it!
Generalities are not that helpful with table design issues.
The more we hear silence, the more we begin to think about our value in this universe.
Paraphrase of Professor Brian Cox.