I've experimented further by adding a very small table to the data source
view that only contains a few dozen records. When I setup a filter based on
a field from the small table, the filter dropdown box populates as it should
when the report is run. This tells me that it can work, but it's not working
when I use a field from a large table. Is it an issue with the amount of
data being retrieved to populate the dropdown box?
This is becoming a real "show stopper" and would greatly appreciate any
assistance.
Thanks...
[quoted text, click to view] "Leighton.d" wrote:
> I'm just getting a Reporting Services server setup. I've purposely started
> with something simple to learn on rather than implementing something complex
> that's difficult to research problems within.
>
> I have a data source that contains one view on the SQL server. I created a
> report that returns the last name and a four digit building code field. If I
> don't implement a filter on the report, all data is returned as expected. I
> added a filter to the report that utilizes the building code field as the
> source, and I set the field parameter to "Prompt" and the operator to "in
> this list".
>
> When I run the report, I'm prompted for the login name and the password, and
> then the building code field filter dropdown box is displayed. When I click
> the dropdown box, no values are displayed. I'm expecting to see the possible
> values for the building code field.
>
> I'm confused as to why when I run the report without a filter, it displays
> the building code in each record, but the filter dropdown box isn't being
> populated when utilized.
>
> Help!!!
>
