****The reason for keeping all the evaluations as one record is because it relates to a certain item that has those evaluations and certain groups (2 other tables)****
That's not a good reason. You should have an idividual record for each evaluation in a related table. Then it's very easy to produce a summary report like:
• Choice1: 2
• Choice2: 4
• Choice3: 1
• Choice1: 4
• Choice2: 0
• Choice3: 1
Your absolutely correct.
..... but I work at a Huge company and I am new to FileMaker and need to create this report ASAP.
Just to reassure you that I wasn't just being lazy.....My logic was that a user reports on the same evaluations for every item and multiple users can share the same item and I needed a calc to calc all evals connected to each user independently and separately based on an algorithm ....so it seemed logical to say "all evaluations for this particular part" dumped into one table...at first.
Any work around help for now would be great. I plan to break the evaluations up in the next version of the database!
IMHO, it would be easier to fix this right now than to try to patch it. I don't see how you can achieve your goal with your current structure without performing 133 calculations (19 evals * 7 choices) and the same number of summaries.
You could perhaps reduce the number of required fields by using repeating fields, or run a script that compiles the summaries into a global field - but none of these are something I would suggest for someone new to Filemaker to try.