Decision Tree

[RycherX]

Is it possible to design this in Access.

I envision a user to open a form that will ask a Y/N question. If user selects"Y" and clicks "next", a different question is asked on the next form. If a user selects "N", user gets routed to a different question.

So the idea is to have a user answer a series of questions driven by a behind the scenes decision rule.

If I store these decision rules in a table, can these rules drive the specific questions?

Moreover, after answering 15 questions, can I store the results of these questions for reporting purposes?

 

[ajetrumpet]

Is it possible to design this in Access.

I envision a user to open a form that will ask a Y/N question. If user selects"Y" and clicks "next", a different question is asked on the next form. If a user selects "N", user gets routed to a different question.

So the idea is to have a user answer a series of questions driven by a behind the scenes decision rule.

If I store these decision rules in a table, can these rules drive the specific questions?

Moreover, after answering 15 questions, can I store the results of these questions for reporting purposes?

as a matter of fact, the rules SHOULD be stored in a table. it would be a waste to write it in code I'm sure. I'm not getting into this, but if you want an idea, here's one:

have a specific set of numbers (1-15) to represent your questions. on answer of the question, use a findrecord() method or something similar to goto the question you want to have answered next. based on a randomization or some predetermined route you have stored in the table. does that make any sense?

 

[RycherX]

as a matter of fact, the rules SHOULD be stored in a table. it would be a waste to write it in code I'm sure. I'm not getting into this, but if you want an idea, here's one:

have a specific set of numbers (1-15) to represent your questions. on answer of the question, use a findrecord() method or something similar to goto the question you want to have answered next. based on a randomization or some predetermined route you have stored in the table. does that make any sense?

If I enable a text box when the user select "Y", I would like the user to comment or elaborate his response. I also want to record his steps for reporting purposes. Is it best to pass the values of his answers from one question to the next. Then commit the values after he reaches the last question and presses "Process".

Or is it better for me to record the data after each time he answers a question?

 

[gemma-the-husky]

in your table that proposes the question have columns for

1 - question no
2 - question
3 - YES answer - a number
4 - NO answer- a number

make the numbers for 3 and 4 point to other questions, then its easy to go to the next question.

----------
if you need to record other data, add extra columns to the table - presumably, you cant get back to a question you have already asked - so there can only be one path through the questions?