Option Groups with 6 options tied to 6 different fields

[dogcrazzie]

Hi, I use access for millions of rows of data and I'm trying to set up a form
with multiple option groups. I think I'm understanding that pretty well
however I do have a couple of can I do this questions. 1. I have one option
box that has 6 choices; IPA, County, City, Zip Code, Tax ID and All. What
I'm trying to do is have them be able to look up a bunch of Doctors based on
one of the above criteria. Each of those 6 options represent a different
field within a query with each of those fields containing tons of different
results. Is that a problem? Do the options have to be representative of one
field? Also, does anyone have any ideas on what the query should look like
to handle the "all" possibility? From each option box I want them to be able
to choose their own criteria building the report per say as they go with the
final showing the results based on those choices. Hope this all made sense.
Would appreciate any assistance. Thanks

 

[KARL DEWEY]

I have one option box that has 6 choices; IPA, County, City, Zip Code, Tax
ID and All.I think you are misunderstanding what an Option Group is. An option group
represents the choices by a number -- 1- IPA, 2- County, 3- City, 4- Zip
Code, 5- Tax ID and 6- All
If you wanted to chose City what else would you do? Would you enter a city
named on your form or pick a city from a list?

 

[Margaret Bartley]

Hi, I use access for millions of rows of data and I'm trying to set up a
form
with multiple option groups. I think I'm understanding that pretty well
however I do have a couple of can I do this questions. 1. I have one
option
box that has 6 choices; IPA, County, City, Zip Code, Tax ID and All. What
I'm trying to do is have them be able to look up a bunch of Doctors based
on
one of the above criteria. Each of those 6 options represent a different
field within a query with each of those fields containing tons of
different
results. Is that a problem? Do the options have to be representative of
one
field? Also, does anyone have any ideas on what the query should look
like
to handle the "all" possibility? From each option box I want them to be
able
to choose their own criteria building the report per say as they go with
the
final showing the results based on those choices.

Create two queries for each of your options (IPA, County, City, Zip Code,
TaxID and All).

One is a GroupBy Totals query that lists all the options in your dataset
for that selection criteria, which is used as the basis of a combo box, so
the user can choose which particular City, Zip code, etc they want. The
other query is based on that combo box. There are a zillion examples of how
to do this, and include an 'all' or "none" option, depending upon what you
are comfortable with. I'm not sure if this is easily done with a macro or
not. I would use Code Behind Form for it.

 

[dogcrazzie via AccessMonster.com]

Yes, sorry I was already mapping the numbers to what the text would be.

I think you are misunderstanding what an Option Group is. An option group
represents the choices by a number -- 1- IPA, 2- County, 3- City, 4- Zip
Code, 5- Tax ID and 6- All
If you wanted to chose City what else would you do? Would you enter a city
named on your form or pick a city from a list?

Hi, I use access for millions of rows of data and I'm trying to set up a form
with multiple option groups. I think I'm understanding that pretty well

[quoted text clipped - 9 lines]

final showing the results based on those choices. Hope this all made sense.
Would appreciate any assistance. Thanks

 

[dogcrazzie via AccessMonster.com]

Everything is already grouped up at the table level. When I did my pull out
of Business Objects (where we download the data from) Each row is already
unique. So are you saying I can't do the all in the same option group? Does
is need to be a seperate box? Not sure what you mean by "Code Behind Form"?
Thanks so much for your assistance I truly appreciate it. Karen

Hi, I use access for millions of rows of data and I'm trying to set up a
form

[quoted text clipped - 16 lines]

the
final showing the results based on those choices.

Create two queries for each of your options (IPA, County, City, Zip Code,
TaxID and All).

One is a GroupBy Totals query that lists all the options in your dataset
for that selection criteria, which is used as the basis of a combo box, so
the user can choose which particular City, Zip code, etc they want. The
other query is based on that combo box. There are a zillion examples of how
to do this, and include an 'all' or "none" option, depending upon what you
are comfortable with. I'm not sure if this is easily done with a macro or
not. I would use Code Behind Form for it.

 

[Rick Brandt]

Everything is already grouped up at the table level. When I did my
pull out of Business Objects (where we download the data from) Each
row is already unique. So are you saying I can't do the all in the
same option group? Does is need to be a seperate box? Not sure what
you mean by "Code Behind Form"? Thanks so much for your assistance I
truly appreciate it. Karen

An OptionGroup is used when you want to offer mutually exclusive choices. If
you think about that it should be apparent that a mutually exclusive choice
is also what you provide with a ListBox or ComboBox.

Now... when using a ComboBox that provides 100 values to choose from would
your table have 100 fields corresponding to those 100 values? Of course
not. It would have one field to hold the value of the selection made from
the list.

An OptionGroup should be used the same way. Two or more mutually exclusive
choices and the value that is selected goes into ONE field in the table.
It's really just a different GUI widget to perform the same task as you
would with a ListBox or ComboBox.

It is when you have multiple choices that are not mutually exclusive that
you would have a field per choice and then you would use separate CheckBoxes
on your form each bound to a field. In that case you would not use an
OptionGroup.