I recently did a survey app for a client. In our case we decided that there would be a limited number of question formats types for example some questions would have a yes no answer and some would have a rating from 1 to 10 type answer.
The design of the app was such that there was a master table for survey templates and then it had a child table of Template Questions. Each question is be identified with the "Format Type" so that ultimately the form knew to behave and decide which fields to expose.
Then when it was time to do the survey we would push a button and it would create survey header records for each recipient (in your case that would be for each employee), and then it would copy the Survey Template child question records onto each individual Employee Survey as Children.
Then because I created a custom Key field for those survey question children it meant that I knew that the survey questions would be numbered say in your case from 1 to 75. That allowed me to make a button on each record which would move either backwards or forwards through those 75 questions. If they moved all the way back they would land on the survey header and once they got past 75 it would land them on a Thank You page.
I grabbed some code of a Kirk Trachy Magic Buttons App to show progress bar at the top of the Question form so they knew how far through the survey questions they they were.
For the rating questions I specifically chose a range of 1 to 10 because that way it can be measured with what is called an NPS (Net Promoter Score) scoring system.
By having the survey questions as children it's much easier to do roll up and counts of yes's and no's and the 1-10 Ratings as summary fields as opposed to hard coding 75 questions on a form.
mark.shnier@gmail.com
QuickbaseCoach.com
