I was kind of hoping for a few very simple create statements but somehow got 50k worth of SQL

A few points:

• Where do the user answers go - none of your tables seem to hold them?
  in the second image there is a responses table I forgot to add in the first one. It holds the personid,surveyid,answerid fields.
• You have a sort order on the valid answers but not one on the questions themselves.
  Yea, I was thinking about adding that functionality. In the previous iteration, but then these requirements changed and at the moment isnt a priority, even though its just a field.
• A user can never enter a free text answer using your system.
  Actually they can. That is what the other field in responses is for. In the actual program QuestionType and AnswerType control what kind of controls are used to create the questions. there is an Other answertype which pops up a dialog box that allows them to freetext their answers. the Response is placed in the other field.
• Would it be worth adding the facility that certain questions are only asked if another question is answered with X?
  Not at this time, these are pretty straightforward survey questions. But it would be something to think about in the future.
• How about grouping your questions into groups. This will make the questionnaire more logical. You could then have a hierarchy of groups (if you wished). A group of questions would only be asked if a question was answered with X etc.
  its not needed at this time, but could be a future enhancement for other surveys
• What is the purpose of the AnswerTypes and QuestionTypes tables?
  these help control how the answers and questions are addressed in the application. ie radiobuttons, checkboxes, freetextfield for questiontypes(which actually formats the answers) answertypes allows for standard answers, additional text, or dropdown field
• Could the tables SurveyQuestions, Questions and QuestionTypes just be one table?
  I dont think so, because there could be multiple surveys that have the same question on them, I could maybe get rid of SurveyQuestions, because there will ever only be one questionid on the same survey. So survey would have a childtable of Questions instead...Questiontypes is needed to determine the type of question, It would not be good normalization to have that as part of the Question Table
• How do you know that a user has finished a survey on an application rather than just quit half way through?
  We dont, other than in the reports when we see they didnt answer all of them. But that will be controlled(as much as possible) through the application itself. As well whether they refused the survey. that will just be a question with a no answer that we can track

Mike