[AccessD] Data-driven option buttons

What you're really wanting then is to build these question gui's on the fly,
right? You want the form to update for each question, according to the
question's parameters, without actually providing the controls during design
time. Um... <gulp>... Did I get that right? 

How many questions are there? Would it be feasible to just build each
question as a subform and load, hide, and unhide as needed? 

Susan H. 

Yup, questions presented one at a time, and perhaps with a few buttons
indicating "next question", "skip this question", "return to unanswered
questions", etc.