Parameters behave as if they are cascading parameters

Hello,
I have created a report which use MS SQL Server 2000 Analysis Services. I am
using MS Reporting Services 2000.
I have 7 parameters, 3 Of them are also linked to olap data source. The
other 4 parameters are non queried. Every parameter has non-queried defaults
and some defaults use expressions and custom code.
The problem is although parameters are not cascading, when I made selection
in combo box all report is refreshed and I parameters are defaulted. This
is the behaviour of cascading parameters but my parameters are not
cascading,
This is realy weird, I always use multiple param in my other reports which
are linked to relational datasources.
Any comments,
Thanks in advance
erdal
sample olap linked param
SELECT
{RS_ns_PX_Time_Hier} ON COLUMNS,
{[Time].Members} ON ROWS
FROM
RSParamsI have recognised that, one Olap linked parameter works fine with other
parameters , but when I add the second olap linked parameter they behave as
if they are cascading but actualy there is no linkage between this two.
"erdal akbulut" <erdalim21@.yahoo.com> wrote in message
news:e9P4L43mGHA.4212@.TK2MSFTNGP04.phx.gbl...
> Hello,
> I have created a report which use MS SQL Server 2000 Analysis Services. I
am
> using MS Reporting Services 2000.
> I have 7 parameters, 3 Of them are also linked to olap data source. The
> other 4 parameters are non queried. Every parameter has non-queried
defaults
> and some defaults use expressions and custom code.
> The problem is although parameters are not cascading, when I made
selection
> in combo box all report is refreshed and I parameters are defaulted. This
> is the behaviour of cascading parameters but my parameters are not
> cascading,
> This is realy weird, I always use multiple param in my other reports which
> are linked to relational datasources.
> Any comments,
> Thanks in advance
> erdal
> sample olap linked param
> SELECT
> {RS_ns_PX_Time_Hier} ON COLUMNS,
> {[Time].Members} ON ROWS
> FROM
> RSParams
>|||It is related with default values, expression type defaults cause this
eventhough expression does not refer to another parameter. I have changed my
default values to queried defaults and the problem has gone.
Not sure if this is documented, I have checkd BOL and could not find
anything maybe somewhere else.
Regards,
"erdal akbulut" <erdalim21@.yahoo.com> wrote in message
news:%234DvI64mGHA.4208@.TK2MSFTNGP04.phx.gbl...
> I have recognised that, one Olap linked parameter works fine with other
> parameters , but when I add the second olap linked parameter they behave
as
> if they are cascading but actualy there is no linkage between this two.
>
> "erdal akbulut" <erdalim21@.yahoo.com> wrote in message
> news:e9P4L43mGHA.4212@.TK2MSFTNGP04.phx.gbl...
> > Hello,
> >
> > I have created a report which use MS SQL Server 2000 Analysis Services.
I
> am
> > using MS Reporting Services 2000.
> >
> > I have 7 parameters, 3 Of them are also linked to olap data source. The
> > other 4 parameters are non queried. Every parameter has non-queried
> defaults
> > and some defaults use expressions and custom code.
> >
> > The problem is although parameters are not cascading, when I made
> selection
> > in combo box all report is refreshed and I parameters are defaulted.
This
> > is the behaviour of cascading parameters but my parameters are not
> > cascading,
> >
> > This is realy weird, I always use multiple param in my other reports
which
> > are linked to relational datasources.
> >
> > Any comments,
> >
> > Thanks in advance
> >
> > erdal
> >
> > sample olap linked param
> > SELECT
> > {RS_ns_PX_Time_Hier} ON COLUMNS,
> > {[Time].Members} ON ROWS
> > FROM
> > RSParams
> >
> >
>