I'm running Access 2003 on Windows XP.
This is more of a developmental/implementation type of question. I have a form which requires answers to 35 different questions. All questions are answered by checkbox and two text fields. This makes for a total of 105 fields (35*3=105) just for question answering. Since all questions require the same Yes/No answer and two text fields, is there a way I can cut down the size of my table?
Should I create a second table to house the answers to each question? The fields in the secnod table could be: Link_ID (to link to the record on my main table), question number, Yes/No field, and two comments boxes. Does this make sense from an implementation perspective, or is there a better solution? I figure that I can add the answers to the secondary table using SQL, so that all the answers could be added to the second table upon form submission. I could then use queries to remerge the data as needed.
Is it better to create a second table or to just use one really LARGE table?
If creating the second table is better, how would I populate the data back into the form’s fields in case a record needs to be updated?
Any advice/direction is greatly appreciated!
Thanks!
-Kyle
This is more of a developmental/implementation type of question. I have a form which requires answers to 35 different questions. All questions are answered by checkbox and two text fields. This makes for a total of 105 fields (35*3=105) just for question answering. Since all questions require the same Yes/No answer and two text fields, is there a way I can cut down the size of my table?
Should I create a second table to house the answers to each question? The fields in the secnod table could be: Link_ID (to link to the record on my main table), question number, Yes/No field, and two comments boxes. Does this make sense from an implementation perspective, or is there a better solution? I figure that I can add the answers to the secondary table using SQL, so that all the answers could be added to the second table upon form submission. I could then use queries to remerge the data as needed.
Is it better to create a second table or to just use one really LARGE table?
If creating the second table is better, how would I populate the data back into the form’s fields in case a record needs to be updated?
Any advice/direction is greatly appreciated!
Thanks!
-Kyle
Comment