<Select all> disappear on server

Hello.
I have a parameter with multi value option.
When I run the report in Visual studio, The first value in the drop
down of this parameter is (Select All).
When I check this option it check all the other values for this
parameter and when I unCheck this value it uncheck all the ther values
for this parameter.
The problem is thet when I'm publishing the report to the server and
then open it in IE the (Select All) value does't appear and I only get
all the other values.
Any body know how to fix this?
Thanks.On Nov 27, 11:08 pm, nicknack <roezo...@.gmail.com> wrote:
> Hello.
> I have a parameter with multi value option.
> When I run the report in Visual studio, The first value in the drop
> down of this parameter is (Select All).
> When I check this option it check all the other values for this
> parameter and when I unCheck this value it uncheck all the ther values
> for this parameter.
> The problem is thet when I'm publishing the report to the server and
> then open it in IE the (Select All) value does't appear and I only get
> all the other values.
> Any body know how to fix this?
> Thanks.
Hi
It might be a service pack issue, here's a link to Microsoft.
http://download.microsoft.com/download/2/B/5/2B5E5D37-9B17-423D-BC8F-B11ECD4195B4/WhatsNewSQL2005SP2.htm

<Select All>

Is there a way to default a multi-value parameter to "Select All"?
Also, can you test to see if the user clicked <Select All>? I want to
display the parameter on the report as the user selecting all.Have you figured it out - default display a multi-value parameter to "Select
All" yet?
"jtstrassburg@.gmail.com" wrote:
> Is there a way to default a multi-value parameter to "Select All"?
> Also, can you test to see if the user clicked <Select All>? I want to
> display the parameter on the report as the user selecting all.
>

<Select a Value> inconsistent

Hi, has anyone else seen this or know of why it's happening?
I have a report with a parameter Region. The region values are pulled
from a query:
select null as id, '' as name
union
select regionid, regionname from region
The Region parameter allows nulls and has a default value of null.
In the visual studio designer everything looks great. The dropdown
parameter is blank and my region values are there if I pull it down.
When I deploy the report to the server, the region parameter looks
different. It now defaults to <Select a Value>. The blank (null) line
exists but is not defaulted to on open of the report.
Another weird aspect of this is that I have a number of other reports
that "seem" to be set up exactly in this manner that work corrrectly
(i.e. The Region dropdown show up blank with valid regions in the
dropdown and no <select a value> option) in the designer and on the
server.
Thanks for your help,
BrettOn your report parameter have you set a non-queried default value of
=Nothing ?
HTH, Magendo_man
"Brett" wrote:
> Hi, has anyone else seen this or know of why it's happening?
> I have a report with a parameter Region. The region values are pulled
> from a query:
> select null as id, '' as name
> union
> select regionid, regionname from region
> The Region parameter allows nulls and has a default value of null.
> In the visual studio designer everything looks great. The dropdown
> parameter is blank and my region values are there if I pull it down.
> When I deploy the report to the server, the region parameter looks
> different. It now defaults to <Select a Value>. The blank (null) line
> exists but is not defaulted to on open of the report.
> Another weird aspect of this is that I have a number of other reports
> that "seem" to be set up exactly in this manner that work corrrectly
> (i.e. The Region dropdown show up blank with valid regions in the
> dropdown and no <select a value> option) in the designer and on the
> server.
> Thanks for your help,
> Brett
>|||Thanks magendo! That worked! I still don't understand why this
parameter acts differently than other parameters (or why setting the
default to NULL does not work), but at this point, I'm just happy it
works. Thanks a bunch.
Brett