I am new to access 2007 and have a project due on Tues & need to know how to set up relationships between my tables. I keep getting errors. Not sure where I'm going wrong.
I am new to access 2007 and have a project due on Tues & need to know how to set up relationships between my tables. I keep getting errors. Not sure where I'm going wrong.
hi Candy, What tables do you have?
Here is a copy of my relationship screen. I finally got them to link, but it doesn't seem like this is the best way to do it. Any advice?
You have player name info in 2 tables. Any fact about a player, of which no player will ever have more than 1, needs to go in the players table. Take this out of Card.
Card should have a field for BrandID, not Brand. Take Brand out, add BrandID. Relate BrandID to BrandID.
Why is the primary key in Team "Team name"? Why not Team ID like the others? I would change that. Of course you will then have to add Team ID to the Card table (and remove Team)
What is City, Team, Position on the Card table? If it is a repeat of data in another table, then it is inappropriate. For that matter, what does City refer to in the Player List? It isn't Team City, is it?
It seems to me that Division is a fact about the Team, not the Player. Right?
Can't a player be on multiple teams during his career? YOu have to make that decision and either take Team out of Player List or leave it there and take it out of Card, relating Team to Player instead of card.
Can a player ever be more than one position during his career?
If so, why is it in the Player List?
If not, why is it in the Card table?
i suspect it is possible, so I would remove Team from Player List.
Keep in mind that a major, major goal of a relational database is to eliminate redundant data.
Thanks for the information...did you get the private message I sent you?
Hi Candy,
Did your instructor give you a suggested number of tables to use in your project? If so, that would help in limiting the scope of the database design. Kimmer's suggestion regarding positions during a player's career (history) is good, but may be beyond the scope or requirements of your project.
Cheers,
I need 4 tables. 20 items in the master table and then at least 3 items in each of the other 3 tables. I have to include things like cost, current value, etc. I am having a ard time with what I should put in each table and ten how to relate them so that I can run the required queries and reports.