Questionnaires

  • Thread starter Thread starter Mark \(InWales\)
  • Start date Start date
M

Mark \(InWales\)

Hello All

I have now been tasked with designing a questionnaire for audit purposes.
Does anyone know of a web resource for examples as I am floundering!

Many thanks
Mark (InWales)
 
The bits I'm floundering on is as follows:

There are over 500 question. These questions can be logically grouped
bringing within the 255 column limit. But do I need one question per column
or perhaps one question per table or even all the questions in one table
(rows) and if the one question per row how do I store the tick box? HELP
I'm really stuck

Many thanks
Mark (InWales)
 
The bits I'm floundering on is as follows:

There are over 500 question. These questions can be logically grouped
bringing within the 255 column limit. But do I need one question per column
or perhaps one question per table or even all the questions in one table
(rows) and if the one question per row how do I store the tick box? HELP
I'm really stuck
Click to expand...

Well Dunae is the real expert on this application since he wrote it, but what
you should do first is study all the tables and the Relationship window. Do
not even look at the various forms and reports at this point. See what
information is in the tables and how they relate. You do NOT want to
put the questions *across* the record in columns! You want to have a
record for each question in the survey. Otherwise, generating nice
statistical reports will be a nightmare.

As Access Jedi Council member John Vinson likes to say:
"Records are cheap, fields are expensive."
 
The bits I'm floundering on is as follows:

There are over 500 question. These questions can be logically grouped
bringing within the 255 column limit. But do I need one question per column
or perhaps one question per table or even all the questions in one table
(rows) and if the one question per row how do I store the tick box? HELP
I'm really stuck
Click to expand...

No. You DON'T need one question per column, or still worse one
question per table <eep!>. You need one question PER RECORD.

Consider three tables:

Questions
QuestionNo Primary Key <don't use an Autnumber, you want to control
the question numbers>
Question Text
<possibly more information, e.g. expected datatype - some questions
might be yes/no, others text, others a date, etc.>

Questionnaires
QuestionnaireID
<information about who filled it out and when>

Answers
QuestionnaireID <link to Questionnaires>
QuestionNo <link to Questions>
Answer <this would be a yes/no "checkbox" field if all questions
are yes/no>

See Duane Hookum's At Your Survey sample database for a working
example of this structure:
http://www.rogersaccesslibrary.com/Otherdownload.asp?SampleName='At Your Survey 2000'


John W. Vinson[MVP]
 
Back
Top