@RedSoxFan,
Hi!
Some of this is data-driven and/or input-driven. E. g. in your grass example, if I say yes, then my understanding is I get response #1. If I say no, it displays answer #2. If I say sometimes, then the display is answer #3.
You would need to show a drop-down menu of choices because you want to limit selections. Otherwise, I, the visitor, could input anything and you would be adding row upon row to your database. With only three choices, you can have it aggregate. There would still be a row in the database for each visitor, but at least there would be limits if you queried it. E. g.
Code:
Row 1 100 Yes responses
Row 2 40 No responses
Row 3 60 Sometimes responses
This also gets you out of anyone clicking past and giving you no answer at all (e. g. the null or empty set).
Would you allow a visitor to return and answer again, or change their answer?
One thing about databases is, they can become enormous rather quickly. For your single question with three responses, if you have 100 people answering it, you are adding 300 rows to your database. If you have 2 questions with 3 possible responses apiece, you get 600 rows, but if you run a report to look at results, you get 3 squared, or 9 entries. To wit:
- Answer 1 = Yes, Answer 2 = Yes
- Answer 1 = Yes, Answer 2 = No
- Answer 1 = Yes, Answer 2 = Sometimes
- Answer 1 = No, Answer 2 = Yes
- Answer 1 = No, Answer 2 = No
- Answer 1 = No, Answer 2 = Sometimes
- Answer 1 = Sometimes, Answer 2 = Yes
- Answer 1 = Sometimes, Answer 2 = No
- Answer 1 = Sometimes, Answer 2 = Sometimes
Then you need something (might even be visual basic? I'm not sure; I have a data background and not a programming one) to display the correct results based upon if X happens, then display Y.
Complex, even though it sounds simple. I think it's possible although you might need for someone to build such a solution.
Stumble It!
Tweet This
Bookmark on Delicious
Share on Facebook
Share on MySpace