One of the data entry forms needed is to be able to enter TblRoster data for
a given year. This is done with a form/subform. The main form is based on
TblYear and the subform is based on TblRoster. A lot is accomplished doing
it this way. It removes the possibility of incorrectly entering HockeyYear
in TblRoster.
It gives you an efficient search for a selected year. It gives you a clean
way to delete all roster data for a selected year. Plus many other benefits.

Steve




"BruceM via AccessMonster.com" u54429@uwe wrote in message
news:a3c497b76f700@uwe...
An ID field that is used as a linking field is like an EmployeeID number.
You can move, change your name, go into a different departemnt, or
whatever.
Through it all your payroll and other history is linked to your EmployeeID
only. Most likely they don't store your name and so forth every time you
get
paid. They store just your EmployeeID, and link to the main Employee
table
to display your name and other information as needed. Likewise player
information exists in the Players table only. Any other time you store
the
Player information you store the single ID field.

Steve showed a table structure that is one way to proceed, given certain
assumptions (although I see no need for a Years table except as a lookup
table, and then only to store the four-digit year without a separate ID
field)