In fairness, (and agreement with marto) you do not look to have put much effort in so far. You need to look into books or web sites which show good database design. No one in their right mind would create a table with 600 columns, one per answer.

As a start, think of the data you need to store and divide it up into relational tables. e.g., a table users storing a username and id, one storing questions and question id, one storing all possible answers and answer ids, and one answers storing user ids, question ids and answer ids. You have the state of answered questions for a user at any time by looking into the rows written into the answers table.

However there are many possible ways of doing this as your research will lead you to find.


In reply to Re: Help on questionnaire by mje
in thread Help on questionnaire by Anonymous Monk

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":



  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.