FM is not necessarily the best application for this.
For quick surveys, use something like Google Forms, or Survey Monkey.
For more elaborate surveys, use LimeSurvey.
OMFG! Thanks Schamblee. You've saved countless hours of programming!
Thanks for the suggestions. I'm integrating the above into a much larger and pre-existing Filemaker solution. Even though Google Forms, Survey Monkey, etc might better as a stand-alone solution I'd really need to build something through Filemaker.
>>integration with FileMaker.
Noted. I'd be interested in how this works for you when deployed.
We have pretty good luck just exporting from LimeSurvey and importing into FM. I think if I needed to I could use ODBC to add the mySQL back-end from Limesurvey to Filemaker, so I could work with the mySQL tables directly.
In general I've been very pleased with the ODBC integration.
I made a small update to show how easy it is to compute average score. You can download the update from the same link above.
for those who need a explanation in the forum which can be text searchable.
A field is a field is a field. Sometimes the field is formatted with a value list on the layout.
ALL of the checked values in checkbox-formatted are put into the field by the order in which they are checked. If you place the same field on the layout, but not format at checkbox, you will see this is a return-delimited list of values.
ANY of the values of radio buttons and are in the field only with ONE value. The way to verify is to put the same field on the layout, but not format as radio, you will see the value change as you click the radio buttons.
We can use this "feature" to make MULTIPLE value lists with one 'value' in each. Then place the same field on the layout and format each one with a single value. Checkboxes and Radio buttons work just as well with this separation. The values that actually are IN the field are as above.
This method allows placement of each checkbox or radio, independently (with or without the label): Horizontal, Vertical, Diagonal, etc. There is greater control of placement and one of the reasons to use this method.
This will work well with static (not changing) value lists, but not with value lists based on a field.