[AccessD] Data-driven option buttons

artful at rogers.com artful at rogers.com
Thu Aug 31 11:08:08 CDT 2006


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

Arthur

----- Original Message ----
From: Rocky Smolin - Beach Access Software <bchacc at san.rr.com>
To: Access Developers discussion and problem solving <accessd at databaseadvisors.com>
Sent: Thursday, August 31, 2006 12:01:09 PM
Subject: Re: [AccessD] Data-driven option buttons

Arthur:

I think simplest would be to create the maximum number of buttons in an 
option frame and hide the ones that aren't being used.

You could adjust the width of the border using select case if you 
wanted, but a borderless option frame would even be easier.

I assume then that the questions will be presented one at a time?

Rocky


artful at rogers.com wrote:
> I think that I have asked this question before, but I can't find anything in my emails that pertains, so...
>
> Assume that a table T1 has several columns C1...C5, containing text, and another column containing an integer. (Let's sidestep the normalization issue, I am aware of that and trying to keep the example simple.) Here is the scenario:
>
> There is a Question column in T1, containing the text of a question to ask the user. The columns C1..C5 contain text representing possible answers to the question, from which the user can select exactly one answer. The integer column stores the number of the answer selected.
>
> For example:
>
> Q: On a scale of 1 to 5, do you consider yourself:
> a) a Genius
> b) quite smart but not a genius
> c) about average
> d) slower than most people I know
> e) smarter than a cucumber but it's close
>
> I would like the interface to present the question and then list its possible answers in the form of a set of option buttons, whose After-Update event will record the number of the option selected. This means that I must a) determine the number of possible answers; b) create that many option buttons (or alternatively create a maximum number and hide the irrelevant ones); and c) populate the labels for the buttons with the text stored in columns C1...C5.
>
> I can't figure out a cool way to do this. Any ideas, friends?
>
> TIA,
> Arthur
>
>
>   

-- 
Rocky Smolin
Beach Access Software
858-259-4334
www.e-z-mrp.com

-- 
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com







More information about the AccessD mailing list