Option Group data display

[Russ]

I've got an option group in a form that saves the numerical choice in
a field in my table. When I create a report on that data how can I
display more meaningful data than what is in the table? For example,
my table will hold a number based upon the option box choice, but the
number itself is not as useful as what the number stands for in text
in my option group. The report will display the number only while I
desire the text.

Table value Text in Option Group
1 Married with children
2 Married no children
3 Single with children

etc.

 

[Access Developer]

Include the link to the lookup Table with the text in the Query that is
RecordSource for your Report, and place the retrieved text Field in the
Control on the Report.

Larry Linson, Microsoft Office Access MVP

 

[Marshall Barton]

I've got an option group in a form that saves the numerical choice in
a field in my table. When I create a report on that data how can I
display more meaningful data than what is in the table? For example,
my table will hold a number based upon the option box choice, but the
number itself is not as useful as what the number stands for in text
in my option group. The report will display the number only while I
desire the text.

Table value Text in Option Group
1 Married with children
2 Married no children
3 Single with children

etc.

... and if the above is not in a lookup table, it should
be. Once you have that table in place, you may want to
consider using a combo box instead of an option group.

 

[Russ]

If it's in a combo box (which is what I did yesterday) then why would
I even have a lookup table? I just entered the values I wanted
displayed and chosen from in the Row Source property of that combo.

 

[Access Developer]

Most of us would use a lookup table because it makes for easier maintenance.
Not always, but often enough, we find ourselves using a combo box to choose
the same values on multiple forms -- and we don't like the idea that we may
have to go back, search out all of those, and change the Value List for each
of those combos and then hope that we didn't miss one or more.

Larry Linson, Microsoft Office Access MVP

 

[Russ]

That sounds logical. Thanks.

Most of us would use a lookup table because it makes for easier maintenance.
Not always, but often enough, we find ourselves using a combo box to choose
the same values on multiple forms -- and we don't like the idea that we may
have to go back, search out all of those, and change the Value List for each
of those combos and then hope that we didn't miss one or more.

Larry Linson, Microsoft Office Access MVP

 

[Russ]

I made my lookup table and created a relationship to the main table
and entered the desired text into the few records I needed. Then I
ran the wizard for the combo box and selected that table to retrieve
the data from. Then when I chose the field that held my records
Access gave me a message saying:
"Data cannot be retrieved from the source you have selected. You must
select a different table or query to continue in the wizard."

With no further explaination. Have you see this before?

 

[Russ]

I did continue with the combo box design without using the wizard, and
it seems to be working ok. I wonder why the wiz didn't like the table
or field I chose?

 

[Access Developer]

I did continue with the combo box design without using the wizard, and
it seems to be working ok. I wonder why the wiz didn't like the table
or field I chose?

If you would describe in detail, perhaps someone could suggest why. Wizards
are intended to expedite development with / use of Access, but they aren't a
substitute for "doing it yourself" in all cases. I use the Combo Box wizard
as a matter of course, and can't remember when I had to go into "do it
myself" mode.

Larry Linson, Microsoft Office Access MVP

 

[Russ]

I found out what was tripping it up this afternoon. I had a couple
copies of the same database in different subdirectories and when I had
my front end pointing to the backend on a table I had not added a
necessary field things went bonk! Added the field and away it went.

 

[Access Developer]

I found out what was tripping it up this
afternoon. I had a couple copies of the
same database in different subdirectories
and when I had my front end pointing to
the backend on a table I had not added a
necessary field things went bonk! Added
the field and away it went.

Glad to hear you found and solved the problem.

Larry Linson, Microsoft Office Access MVP