Definitely consider what @lindsay_knowcode recommends.
If in fact, you are building a form builder product, the basic schema is is 3 primary datasets like this (subject to exact use case of course):
- Questions - will store the text of the question, the answer type and a number range (potentially as 2 fields) for numeric answers and text inputs (number of chars) and a list of answers for dropdowns / radio buttons etc. (prob also question order and potentially a linked form dataset if you want questions to be grouped under a form)
- Answers - only for dropdown / radio buttons (or for all answers for dynamic forms) mostly a text field for the answer and a sort number and a numeric value associated with answer (for grading or determining certain categories) and/or a question associated with the answer if you want to have dynamic questions.
- Responses - this is for user’s response. contains the user, question and answer (decision has to be made how to store dropdown / radio button answers if you use the text of the answer or the answer record)