cascading parameters

I am a little confused on these cascading parameters.
Can I use them with stored procs and how?
I have one main stored proc and many smaller ones for the parameters.
I seem to be missing where to link them?Cascading parameters means one parameter is dependant on a different
parameter.
Like you have to choose a Country before a drop down list of Cities in that
country gets selectable.
You make cascading parameters by having the query for the second parameter
take the value of the selected item of the first parameter as a parameter.
Pseudocode:
Parameter 1 - Country
Select CountryID, CountryName from Country
- Parameter Value = CountryID, Parameter Label = CountryName
Parameter 2:
Select CityID, CityName from City where CountryID = Parameters!Country.Value
When you connect parameters, you won't be able to choose a city before
you've chosen a country.
You link the second parameter to the first just as you would link a data set
to the parameters.
Kaisa M. Lindahl Lervik
"ATB4U" <ATB4U@.discussions.microsoft.com> wrote in message
news:35B6AA90-3871-4DA5-A05D-B1BDD9E8EB33@.microsoft.com...
>I am a little confused on these cascading parameters.
> Can I use them with stored procs and how?
> I have one main stored proc and many smaller ones for the parameters.
> I seem to be missing where to link them?
>|||Thank you for the reply.
I am using stored procs everywhere and having a time trying to link them.
I can get part of the parameter to do what I want it's at execution it fails
to work.
Will try to make my parameters link, currently there is no relationship. If
you select a certain group you get a set of med conditions and they are not
tied to each other on the backend?
Will keep trying though...thx again..it was very helpful.
"Kaisa M. Lindahl Lervik" wrote:
> Cascading parameters means one parameter is dependant on a different
> parameter.
> Like you have to choose a Country before a drop down list of Cities in that
> country gets selectable.
> You make cascading parameters by having the query for the second parameter
> take the value of the selected item of the first parameter as a parameter.
> Pseudocode:
> Parameter 1 - Country
> Select CountryID, CountryName from Country
> - Parameter Value = CountryID, Parameter Label = CountryName
> Parameter 2:
> Select CityID, CityName from City where CountryID = Parameters!Country.Value
> When you connect parameters, you won't be able to choose a city before
> you've chosen a country.
> You link the second parameter to the first just as you would link a data set
> to the parameters.
> Kaisa M. Lindahl Lervik
>
> "ATB4U" <ATB4U@.discussions.microsoft.com> wrote in message
> news:35B6AA90-3871-4DA5-A05D-B1BDD9E8EB33@.microsoft.com...
> >I am a little confused on these cascading parameters.
> > Can I use them with stored procs and how?
> > I have one main stored proc and many smaller ones for the parameters.
> > I seem to be missing where to link them?
> >
>
>|||I have something working but what can I set the true property to?
=IIF(left(Parameters!MonGrp.Value,2) = "BB", Nothing,"exec p_GetConditions")
causing an error: ExecuteReader: CommandText property has not been initialized
This is exciting help pls on this last endeavor.
"ATB4U" wrote:
> Thank you for the reply.
> I am using stored procs everywhere and having a time trying to link them.
> I can get part of the parameter to do what I want it's at execution it fails
> to work.
> Will try to make my parameters link, currently there is no relationship. If
> you select a certain group you get a set of med conditions and they are not
> tied to each other on the backend?
> Will keep trying though...thx again..it was very helpful.
> "Kaisa M. Lindahl Lervik" wrote:
> > Cascading parameters means one parameter is dependant on a different
> > parameter.
> > Like you have to choose a Country before a drop down list of Cities in that
> > country gets selectable.
> > You make cascading parameters by having the query for the second parameter
> > take the value of the selected item of the first parameter as a parameter.
> >
> > Pseudocode:
> >
> > Parameter 1 - Country
> > Select CountryID, CountryName from Country
> > - Parameter Value = CountryID, Parameter Label = CountryName
> >
> > Parameter 2:
> > Select CityID, CityName from City where CountryID = Parameters!Country.Value
> >
> > When you connect parameters, you won't be able to choose a city before
> > you've chosen a country.
> > You link the second parameter to the first just as you would link a data set
> > to the parameters.
> >
> > Kaisa M. Lindahl Lervik
> >
> >
> > "ATB4U" <ATB4U@.discussions.microsoft.com> wrote in message
> > news:35B6AA90-3871-4DA5-A05D-B1BDD9E8EB33@.microsoft.com...
> > >I am a little confused on these cascading parameters.
> > > Can I use them with stored procs and how?
> > > I have one main stored proc and many smaller ones for the parameters.
> > > I seem to be missing where to link them?
> > >
> >
> >
> >|||You can only cascade (link) parameters that have a relation. That's sort of
the point. What you choose as the value in the first parameter, get sent to
the query for the next parameter as a parameter.
Microsoft has written a tutorial on "Adding cascading parameters to a
report" at
http://msdn2.microsoft.com/en-us/library/aa337426.aspx
You might want to read it to get a clear picture on what it is and how to
use it in your report. :)
Kaisa M. Lindahl Lervik
"ATB4U" <ATB4U@.discussions.microsoft.com> wrote in message
news:6FCEEC06-0591-4C4F-B10C-360DEE2B21CD@.microsoft.com...
>I have something working but what can I set the true property to?
> =IIF(left(Parameters!MonGrp.Value,2) = "BB", Nothing,"exec
> p_GetConditions")
> causing an error: ExecuteReader: CommandText property has not been
> initialized
> This is exciting help pls on this last endeavor.
> "ATB4U" wrote:
>> Thank you for the reply.
>> I am using stored procs everywhere and having a time trying to link them.
>> I can get part of the parameter to do what I want it's at execution it
>> fails
>> to work.
>> Will try to make my parameters link, currently there is no relationship.
>> If
>> you select a certain group you get a set of med conditions and they are
>> not
>> tied to each other on the backend?
>> Will keep trying though...thx again..it was very helpful.
>> "Kaisa M. Lindahl Lervik" wrote:
>> > Cascading parameters means one parameter is dependant on a different
>> > parameter.
>> > Like you have to choose a Country before a drop down list of Cities in
>> > that
>> > country gets selectable.
>> > You make cascading parameters by having the query for the second
>> > parameter
>> > take the value of the selected item of the first parameter as a
>> > parameter.
>> >
>> > Pseudocode:
>> >
>> > Parameter 1 - Country
>> > Select CountryID, CountryName from Country
>> > - Parameter Value = CountryID, Parameter Label = CountryName
>> >
>> > Parameter 2:
>> > Select CityID, CityName from City where CountryID =>> > Parameters!Country.Value
>> >
>> > When you connect parameters, you won't be able to choose a city before
>> > you've chosen a country.
>> > You link the second parameter to the first just as you would link a
>> > data set
>> > to the parameters.
>> >
>> > Kaisa M. Lindahl Lervik
>> >
>> >
>> > "ATB4U" <ATB4U@.discussions.microsoft.com> wrote in message
>> > news:35B6AA90-3871-4DA5-A05D-B1BDD9E8EB33@.microsoft.com...
>> > >I am a little confused on these cascading parameters.
>> > > Can I use them with stored procs and how?
>> > > I have one main stored proc and many smaller ones for the parameters.
>> > > I seem to be missing where to link them?
>> > >
>> >
>> >
>> >|||Here's the great thing!
I got this to work, conditional data set.
=IIF(left(Parameters!MonGrp.Value,2) = "BB",Nothing,"exec p_GetConditions")
What I am looking for now if the user selects BB, I need to hide the
condition parameter...something in the "Nothing" piece that diables the
condition parameter.
Thank you for all your help, but I have to get this b/c it will be needed
throuhout all of my reports.
"Kaisa M. Lindahl Lervik" wrote:
> You can only cascade (link) parameters that have a relation. That's sort of
> the point. What you choose as the value in the first parameter, get sent to
> the query for the next parameter as a parameter.
> Microsoft has written a tutorial on "Adding cascading parameters to a
> report" at
> http://msdn2.microsoft.com/en-us/library/aa337426.aspx
> You might want to read it to get a clear picture on what it is and how to
> use it in your report. :)
> Kaisa M. Lindahl Lervik
>
> "ATB4U" <ATB4U@.discussions.microsoft.com> wrote in message
> news:6FCEEC06-0591-4C4F-B10C-360DEE2B21CD@.microsoft.com...
> >I have something working but what can I set the true property to?
> > =IIF(left(Parameters!MonGrp.Value,2) = "BB", Nothing,"exec
> > p_GetConditions")
> > causing an error: ExecuteReader: CommandText property has not been
> > initialized
> > This is exciting help pls on this last endeavor.
> >
> > "ATB4U" wrote:
> >
> >> Thank you for the reply.
> >> I am using stored procs everywhere and having a time trying to link them.
> >> I can get part of the parameter to do what I want it's at execution it
> >> fails
> >> to work.
> >> Will try to make my parameters link, currently there is no relationship.
> >> If
> >> you select a certain group you get a set of med conditions and they are
> >> not
> >> tied to each other on the backend?
> >> Will keep trying though...thx again..it was very helpful.
> >>
> >> "Kaisa M. Lindahl Lervik" wrote:
> >>
> >> > Cascading parameters means one parameter is dependant on a different
> >> > parameter.
> >> > Like you have to choose a Country before a drop down list of Cities in
> >> > that
> >> > country gets selectable.
> >> > You make cascading parameters by having the query for the second
> >> > parameter
> >> > take the value of the selected item of the first parameter as a
> >> > parameter.
> >> >
> >> > Pseudocode:
> >> >
> >> > Parameter 1 - Country
> >> > Select CountryID, CountryName from Country
> >> > - Parameter Value = CountryID, Parameter Label = CountryName
> >> >
> >> > Parameter 2:
> >> > Select CityID, CityName from City where CountryID => >> > Parameters!Country.Value
> >> >
> >> > When you connect parameters, you won't be able to choose a city before
> >> > you've chosen a country.
> >> > You link the second parameter to the first just as you would link a
> >> > data set
> >> > to the parameters.
> >> >
> >> > Kaisa M. Lindahl Lervik
> >> >
> >> >
> >> > "ATB4U" <ATB4U@.discussions.microsoft.com> wrote in message
> >> > news:35B6AA90-3871-4DA5-A05D-B1BDD9E8EB33@.microsoft.com...
> >> > >I am a little confused on these cascading parameters.
> >> > > Can I use them with stored procs and how?
> >> > > I have one main stored proc and many smaller ones for the parameters.
> >> > > I seem to be missing where to link them?
> >> > >
> >> >
> >> >
> >> >
>
>