I didn't give you any code, only suggested table names and contents.
I assumed a more advanced level on your part. What I'm suggesting may
seem like quite a stretch.
I assume that you have a different source for questions and that the
answers are then collected from the respondents (actually, the answers
could be put directly into the database by the respondents after you
have established the names (A,B,C, etc.) for each question).
Design two new tables:
tblQuestion should be a list of every question you're going to ask.
Its Primary Key should be an Autonumber field named QuestionID,
another field, Question, for the actual question, text 255. If you
think your questions may run to 256 characters or more, change the
datatype of field from Text to Memo.
tblAnswer will hold all of the answer names and later, all of the
actual answers. Its PrimaryKey should be QuestionID, an autonumber
field. It will also have a Long Integer field named QuestionID. That
field will be a foreign key on tblQuestion that links this Answer to
that Question (don't worry about it, just do it and later learn why it
works that way. When everything else is working properly this field
will be filled in for you. Next will be a field, Answer, text 20.
(you only need one character if they'll always be single character
names. Next will be a field for the answer, Answers, it will be type
Yes/No (Boolean)
Go to Tools|Relationships and show the above two tables. Draw a line
between tblQuestion.QuestionID to tblAnswer.QuestionID. Doubleclick
that line. Click enforce Referential Integrity and Cascade deletes.
the relationship is One - tblQuestion to Many -tblAnswer.
in the Database|tables window, select tblQuestion and then click the
AutoForm Wizard Icon. It Will design you a fairly simple form. Make
the textbox for the Question fairly large.
Drag the bottom of the form downward by more than the size of the
question guest textbox so that you have a large space.
Go back to Database|tables and select tblAnswer. Click the Autoform
Wizard Icon and let it create a very simple form for you. Open the
form in design mode. If the form's header and footer are visible,
turn them off. re-design what's left so that it fits into one line
across. In the form's properties make it's default view "continuous".
Save this form giving it a name something like "sufAnswer"
Open form Question in design view and then hit the restore button so
that you can see the database window behind the form. Find sufAnswer
in the Database|Forms window and drag it into the blank area below the
textbox on formQuestion. Save the form. Twiddle with it to get a
somewhat usable appearance and then start to test it.
Enter your first few questions in the Question textbox on the main
form. Pay no attention to the subform just yet. After you have
entered 5 questions or so then close the form and then re-open it. By
what ever means you determine, decide what answer names belong to each
question. You'll notice that as soon as you start to enter data in
one subform record another record is presented. (that record will go
away if you put no data into it).
When you get that much working you're well on your way to knowing how
to handle these few issues - you'd be surprised how often they come up
if you continue to create Access applications.
If my explanations of the creation and integration of the form/subform
left you dizzy or were just plain wrong, there is some pretty good
stuff in Access help that walks you through the same steps. Look for
Subform/subreport.
There are lots of places to get bits of Access lore: this newsgroup
and several others, especially tablesdesign, forms, formscoding and
the ever popular gettingstarted. Check out
www.mvps.org/access for
lots of advice and goodies.
HTH
