1) did you look here for a question db model - http://www.databaseanswers.org/data_models/
2) info on normalization, which you should read if not familiar (we might suggest the perfect schema, but how would you create your own next time?)
b) and a bunch of other good stuff...
Normalization Parts I, II, III, IV, and V
http://rogersaccessblog.blogspot.ca/...on-part-i.html
and/or
http://holowczak.com/database-normalization/
Entity-Relationship Diagramming: Part I, II, III and IV
http://rogersaccessblog.blogspot.ca/...ng-part-i.html
How do I Create an Application in Microsoft Access?
http://rogersaccessblog.blogspot.ca/...cation-in.html
Important for success:
One source about how to name things - http://access.mvps.org/access/general/gen0012.htm
What not to use in names - http://allenbrowne.com/AppIssueBadWord.html
About Auto Numbers
- http://www.utteraccess.com/wiki/Autonumbers
- http://access.mvps.org/access/general/gen0025.htm
The evils of lookup fields - http://access.mvps.org/access/lookupfields.htm
Table and PK design tips - http://www.fmsinc.com/free/newtips/primarykey.asp
3) to me, it seems the schema would resemble
tblAcct |
|
AcctID |
AcctName |
1 |
Acme |
2 |
Apex |
3 |
Alcoa |
tblQuestion |
|
Qid |
Question |
1 |
What is your name? |
2 |
Favorite color? |
3 |
Who's yer Daddy? |
tblAcctQuestion |
AcctQ_ID |
Acct_FK |
Quest_FK |
1 |
1 |
2 |
2 |
1 |
3 |
3 |
2 |
1 |
4 |
3 |
2 |
Account 1 is asked q's 2 & 3. 2 is only asked q1, and 3 is only asked 2 (based on the values shown in the linking table tblAccountQuestion).
If you wanted to report on who gets asked q2, it should be easy. I'm not seeing a need for a whole bunch of code...
EDIT: forgot you'd need a notes table, but if you get the drift and I'm on the right path, you can probably figure out how that fits in. At least you should be able to after studying normalization.
The more we hear silence, the more we begin to think about our value in this universe.
Paraphrase of Professor Brian Cox.