A family of Microsoft relational database management systems designed for ease of use.
Does the awards table into which you are entering the data reference a separate entrants table? It should. Also, can each award be entered by more than one entrant? If not the relationship type is one-to-many so you need tables in broad outline like this:
Entrants
....EntrantID (PK)
....FirstName
....LastName
....etc
Awards
....AwardID (PK)
....Award
....EntryDate
....EntrantID (FK)
Otherwise the relationship type is many-to-many, so the model would be:
Entrants
....EntrantID (PK)
....FirstName
....LastName
....etc
Awards
....AwardID (PK)
....Award
and to model the relationship type by resolving it into two one-to-many relationship types:
AwardEntants
....AwardID (FK)
....EntrantID (FK)
....EntryDate
The primary key of the last table is a composite one of the foreign keys AwardID and EntrantID if each entrant can enter the same award only once. If, on the other hand, each entrant can enter the same award more than once on different dates the primary key is a composite one of all three columns.
For data entry the interface should, in both scenarios be, as Duane says, a parent form and subform. The parent form can be based on Entrants or on Awards depending on how you wish to enter the data. In the first scenario the subform would be based on the other table. In the second scenario it would be based on AwardEntants.
You'll find an example of a basic many-to-many relationship type as ParentActivities.zip in my public databases folder at:
https://onedrive.live.com/?cid=44CC60D7FEA42912&id=44CC60D7FEA42912!169
If you have difficulty opening the link copy its text (NB, not the link location) and paste it into your browser's address bar.
This little demo file includes forms/subforms for entering activities per parent or parents per activity.