Draw pictures of your tables and their relationships to one another. Keep you tables atomic, no duplicate data. Duplicate foreign keys are ok.
If you don't get that right, you have problems.
Tables:
tbPlayers
PlayerID
sLastName
sFirstName
sStree1
sStree2
CityID
StateID
tbTelephone
TelephoneID
PlayerID
TelephoneTypeID
sTelephone Number
tbTelephoneTypes
TelephoneTypeID
sTelephoneType
tbCities
CityID
sCity
tbStates
StateID
sState
tbSports
SportID
sSport
tbHistory
PlayerID
SportID
AgeGroupID
TeamID
Year
tbAgeGroups
AgeGroupID
sAgeGroupDescription
tbTeam
TeamID
SportID
YearID
AgeGroupID
sTeamName
tbTeamRoster
TeamID
YearID
PlayerID
tbYearsTracked
YearID
sYear
tbTeamRecord
RecordID
YearID
TeamID
OpposingTeamID
dtDateOfGame
RefereeID
sScore
sStatistics
etc.
tbReferee
RefereeID
sRefereeLastName
sRefereeFirstName
This could go on and on . . .
My experience is that teams keep the same name, year after year, the players and the teams played changes..
The foregoing ought to get you started. I don't guarantee that it's perfect, but it's a start. Draw a picture of the tables and how they relate to one another. You'll see the beauty of a normalized realtional database.
Access will whiz through it.
Bon chance.