Is this redundant? NFL Draft DB

[GenericHbomb]

It has been a little while since the last time I created a database. I recently got tasked with creating a database that tracks the first 3 rounds of the 2011 Draft.
• Your database must have the following attributes and functionality:
It must run via a switchboard
It must allow for the input of athletes and their identifying data and contain at least the following:
Name
College
Draft Round Number
Position


NFL Team
At minimum, the following reports must be available:
Report of a query to find draftees by round
Report to list draftees by team
Report to list draftees by position
Report of a query to show draftees college
Report of a query to find athletes by name

I just started planning it out but here is what I have for tables
TBL: Player (last name, first name, height, weight, grade)
TBL: College (College)
TBL: DraftRound (Rounds)
TBL: Position (Position)
TBL: NFLTeam (NFL teams)

Every player has a college, draft round, position and drafted team. All four of those will repeat at least once throughout because there are only a limited number of positions, draft rounds, nfl teams and colleges.
Do I need this many tables to avoid redundancy or is this overkill?

[alansidman]

To be honest, I think it can all be done in one table. The tables for college, position, nfl, and rounds can be used as lookup tables if you deem them necessary. But since you are only doing 3 rounds, I don't see that as being needed. All those items can be placed in your primary table. You should be able to run your queries getting all your data as desired.

Alan

[GenericHbomb]

I just wanted to say thanks for your response. I went with using only one table and the database worked really well! Thanks!