List Box in a Report

[Guest]

I have a list box in a report footer, which has 5 rows and 3 columns
column names are Charity name, % to Pay, Year It is based on a query with
year as criteria
I would like to be able to put a text box next to each row and have it show
the % to pay. Row(1) Column(2)
Row(2) Column(2)
Row(3) Column(2) and continue on with each row
I have tried everything I think, but nothing works.
Any help is appreciated
Thanks for any help

Roger

 

[Van T. Dinh]

Other may disagree with me but IMHO, ListBox is an *interactive* Control
suitable for user interactions on Access Forms but not for static Reports.
Thus, I don't use ListBox in Reports. I have done a number of databases
with lots of Reports and I never needed ListBoxes (or ComboBoxes) in
Reports.

Perhaps, a SubReport is more appropriate in your case?

 

[Guest]

What I'm trying to do is multiply the % times the amount avaible to pay to a
charity
I have the Sum avaible in the report footer, thus the reason for trying to
pull the % number from the list box, is there a way I can multily the % like
=[TextBox99]*[ListBox87].Row(1).Column(2)
Thanks for your help

 

[Larry Linson]

What I'm trying to do is multiply the % times the amount avaible to pay to
a
charity
I have the Sum avaible in the report footer, thus the reason for trying to
pull the % number from the list box, is there a way I can multily the %
like
=[TextBox99]*[ListBox87].Row(1).Column(2)
Thanks for your help

Other may disagree with me but IMHO, ListBox is an *interactive* Control
suitable for user interactions on Access Forms but not for static
Reports.
Thus, I don't use ListBox in Reports. I have done a number of databases
with lots of Reports and I never needed ListBoxes (or ComboBoxes) in
Reports.

Perhaps, a SubReport is more appropriate in your case?

I agree with Van that a Control intended to be interactive, e.g., a List
Box, does not belong in a static Report. But, if you feel compelled to use
one, check help on ListItem, ItemData, and Column, a combination of which
may allow you to address the issue you described.

Larry Linson
Microsoft Access MVP