If you have no further requirements, then it doesn't really matter how you store it. Until you know *how* you're going to use the information, then there's no use in speculating about the "best" way. As you know more about what you're going to do with the data, you'll get clues on how best to structure it.
For example: If *all* your reports are keyed from the user ID, then a single flat table (or flat file) may be perfectly sufficient. If the questions are grouped into categories and you report based on categories, you'll want to find a way to separate the questions...such as a different table for each category. If you find that questions are continually being added to the system, you'll probably want to put the question definitions into a table, etc.
So think about the entirety of the problem, then figure out what scheme will help you make the simplest (to write and maintain) code. Give a slight nod to expected "expansion" by not making design decisions that make expected changes too difficult.
...roboticusIn reply to Re: Help on questionnaire
by roboticus
in thread Help on questionnaire
by Anonymous Monk
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |