Following-up after Chris Hajer's suggestion to create a unique post. Ultimately, what I'm trying to do, and what I believe is a starting point for the solution is documented in the link/thread below that I copied and included below:
I know some time has elapsed since you last responded to this post, but I was hoping to get your thoughts on something of an extension of this example. I have a pretty basic quiz (30-questions) with each item on the quiz having a possible value between 1 and 10. What I'd like to do is to use a required numeric (number field) to capture the totals.
Currently I have the quiz paginated (10 questions per section) but it doesn't have to be that way. My goal would be to provide a section score (if I can use pagination) and an aggregate score (upon submission of the form).
The end-user could then (manually) compare against a range to see how they stack up (e.g. you scored 250, see the chart below to see what this means) or ideally I'd do that programmatically as well (you scored 250 that means you are awesome) - and it looks like your logic would get me most of the way, but with a possible scoring range between 30 and 300, it could be a pretty daunting/messy task to write the case logic, at least the way you have it in your code.
Here is the link to the work-in-progress: http://www.getmejamienotter.com/humanize/courageousness/
And here is the original link to what I think is the solution and my first post, suggesting that I post here:
Any thoughts or ideas?