I think you need to modify the structure of your database so that you do not have a single check box field with 50 values in it. If you replace it with a related table of up to 50 records for each person--1 for each value selected for that person, producing your summary report becomes much easier to do.
OK - I think I see what you mean but would this work if the "person" is repeated multiple times?
The real purpose is that I have a DB in which Contractors are issues "safety notices" so the contractors are the same set of four names but the safety issues (colors in my earlier example) change each time a new "violation" is written. Each contractor can receive multiple violations a day with different violation categories - we're trying to create a trending report to show where the contractors need to improve.
Your help is much appreciated!!
I see no reason why it wouldn't work. You'd set up some tables in a many to many relationship like this:
Contractors would be one record for each contractor.
Violations would list each of your 50 violation types (and adding/changing them is now a data entry job, not a programmer's)
Contractor_Violation has one record for each and every safety notice issued for a contractor.
Contractors::ContractorID = Contractor_Violation::ContractorID
Violations::ViolationID = Contractor_Violation::ViolationID
You'd use a portal to contractor_Violation with fields added from Violations on your contractors layout to issue safety notices for that contractor.
A more sophisticated structure could include a projects table for cases where you need to manage this for more than one project.