It appears to me that you have a many to many relationship.
A given film is reviewed by more than one person, but a given person reviews more than one film. Thus, you would use a third, join table, to link the two in a many to many relationship:
Committee::__pkCommitteeID = Committee_Film::_fkCommitteeID
Films::__pkFilmID = Committee_Film::_fkFilmID
For an explanation of the notation that I am using, see the first post of: Common Forum Relationship and Field Notations Explained
With these relationships, you can place a portal to Committee_Film on your Films layout to list all committee records linked to that one Film Record. Fields from Committee can be included to show additional info such as the reviewer's name. Fields in Committtee__Film can be defined to hold info specific to that one reviewer's review of a given film if that is of use for this process.
That's definitely getting me closer, and I'll continue to play around with it. The issue really is I want Committee Names listed whether they've rated that film or not. So, all 9 committee members will be listed for every film - then during meetings I can quickly click on the radio button for their rating of the film we're discussing.
I originally had fields for ratings within the Film table which worked, but if the committee members change at any point it will be a headache updating everything.
The individual ratings would be recorded in fields in the join table. If a member has not yet rated a film, you will know because that field is blank.
You can use a script to populate the join table for each film record at the time you add a new record in Films to save the need of creating individual records by hand for each film.
I hadn't thought of using a script to create the empty records, that's perfect! Thanks again for the great solution Phil