The inability to produce reports or summarize on these multiple fields is one major reason that your Exercises should be related records and not fields.
Any time you find yourself creating multiple 'like' fields, such as Exercise1, Exercise2, etc, it is red flag that you are mis-structuring. Each exercise should be a record in the Workout table instead which would look like this:
WorkoutID (unique auto-enter FM-generated meaningless serial)
ExerciseID (foreign key which is the primary ID from your Exercises table)
CustomerID (foreign key which is the primary ID from your Customers table)
You may want additional fields in this workout schedule such as duration, repetitions ... anything else specific to the workout.
When you have this structured properly, you then isolate your customer records (either by performing a search in the Workout table or by issuing a Go To Related 'from customer to Workout). You would then generate your report easily because the exercise is a record. You would place ExerciseName, Description and Photo fields from Exercises directly on the Workouts layout. Since they are related by ExerciseID, the information will display in Workouts.
If you wish to see an example, I would be happy to provide one.
I have it figured out now.
Always seem to get ahead of myself creating pretty layouts and fancy reports without thinking about the foundations first!