Struggling to create questionnaire form layout

[antimoneylaundering]

Hey all-

New Access user here. I need to create a questionnaire form and I'm not sure how to go about it. I want the Y,N, and N/A to be radio buttons.
It should like like the table below, but substantially larger:

Stage A
Step 1	Yes	No	N/A
Step 2	Yes	No	N/A
Step 3	Yes	No	N/A

Stage B
Step 4	Yes	No	N/A
Step 5	Yes	No	N/A
Step 6	Yes	No	N/A

Both of those fields (Stage and Step) are lookup fields from a separate Stage Table and separate Step Table.



How do I get this formatting?

[June7]

Seldom does a user-friendly questionnaire form resemble a normalized database structure.

The radio buttons should be part of an Option Group control. The Option Group control should be bound to field.

Search web, there appear to be numerous YouTube how-tos.

[antimoneylaundering]

Seldom does a user-friendly questionnaire form resemble a normalized database structure.

Why is that exactly? What are the particular hurdles between making a questionnaire user friendly and being able to build a decent database out of it? I read the following on another forum in regards to questionnaires:

"This is a common enough problem that I call it the "questionnaire trap". It'sa very natural thing to just add another column/field for each question.

But it is WRONG.

Think about it: suppose down the road you need to add two more questions. You
open your table in design view, change the structure of the table, save it;
change the design of all your queries; change the design of all your forms;
change the design of all your reports... oops! database corrupted, where's my
backup disk...

Data (such as the identity or text of a question) should go *in a field in a
table*, not in a fieldNAME.

The proper structure would have;

Questionnaires
QID <Primary Key>
<information about the person filling out this instance of the
questionnaire>

Questions
QuestionNo
QuestionText

Answers
QID <whose questionnaire is this>
QuestionNo <what question are they answering>
Answer <integer or text or whatever is appropriate in your case>

Rather than one FIELD per answer, you will have one RECORD per answer."The theory makes sense to me, but I don't know how to transpose that principle to my questionnaire form.

All of the tasks are unique, so I don't need to worry about stage much because I can theoretically just use a text box. I previously googled radio buttons and understand how they work, I just need the Task, and then I can bind the radio buttons to them. I also need to create a calculated field for each form. In this field I will need to deduct X number of points when "No" is selected. "X" is dependent upon the task selected, not all tasks have the same point value. I'll tackle that after I figure out the formatting, I first want to be sure the formatting is conducive to that.

I really appreciate all of your help. I'm very new at this, and really appreciate you all for taking the time to walk me through it.

[June7]

That excerpt pretty much says it.

Imagine a questionnaire (a paper document you hand to a person) which often has items (tasks or whatever) listed vertically with questions as columns and person responds simply with yes/no under each column for each item. Or maybe the reverse is true - questions are listed vertically and the items are columns. Maybe user can check under only one of the columns for each row (I see this a lot in web-based surveys). These may be user-friendly but are not normalized structure for db design. A data entry form for a questionnaire database implementing relational and normalized structure would not look like those documents.

I am not saying a paper questionnaire can't mimic the data entry form, just that they often don't.

I don't know enough about your data to advise on specifics. Maybe this tutorial will help http://www.rogersaccesslibrary.com/

[antimoneylaundering]

I've attached a generic version of my database. It should be really simple. I created a task field for each task. Then I created a bound group with radio buttons. I stored the values from the task table in the option group. I need to be able to link Task A on the form to Task A on the table. Essentially I want to be able to pull data from it, such as how often we complete Task A. I don't believe I can do so as is. How do I update this to pull that data? I tried messing with the control source and that didn't seem to work. As mentioned previously I'm going to need to create a calculated field based on the Yes. No, N/A fields. This is going to be updated over time so I want to go about this in a way that it will be able to do so without messing up the database. I've scoured the internet and haven't found a way to bound an option group to a specific cell in a field. This may be because I'm new enough I don't know how to search effectively. Some of the examples provided are more complex and I'm struggling to apply them to this specific scenario.


Database9.zip

[ssanfu]

I would suggest that you use pencil and paper/whiteboard/cardboard/sticky pads/etc to design your dB first, before you try and create tables/queries/forms.

One method I saw was to use unbound forms and write (a lot of) code to save the data (the answers).

I would consider a questionnaire to be the same as a survey, so:
Duane Hookom has created a dB named "At Your Survey" (I have not looked at it) that might help you understand what would be involved in creating your questionnaire dB. There is an Access 2000 format that could be converted to A2010. Please read the description on the link page......
See http://www.rogersaccesslibrary.com/f...ey_topic3.html