Yes, Teo is correct. In case of cascading/hierarchical parameters, there
will be SOAP calls for every dependent parameter change. Since the calls are
"Teo Lachev [MVP]" <teo.lachev@nospam.prologika.com> wrote in message
news:OUppOuxsEHA.2300@TK2MSFTNGP09.phx.gbl...
> Karl,
>
> I think that a new instance is created in your case because the HTML
viewer
> reposts the report back to the Report Server when the dependent parameter
is
> changed. Why don't you try an expression-based query with IN clause?
>
> --
> Hope this helps.
>
> ---------------------------------------------
> Teo Lachev, MVP [SQL Server], MCSD, MCT
> Author: "Microsoft Reporting Services in Action"
> Publisher website:
http://www.manning.com/lachev > Buy it from Amazon.com:
http://shrinkster.com/eq > Home page and blog:
http://www.prologika.com/ > ---------------------------------------------
>
> "Karl Prosser" <klumsy@xtra.co.nz> wrote in message
> news:7156880c.0410142026.32ffb136@posting.google.com...
> > Does anyone know when a custom assembly instance is created?
> > i had thought once per report.
> > however i have some custom code using the custom assembly inside
> > parameters name and values list, and it seems that whenever a earlier
> > cascading parameter is changed (and thus the dependand parameters will
> > have to be reentered/calculated) a NEW instance of the custom assembly
> > class is created which is quite annoying? is this true, or just my
> > misinterpretation.
> >
> > what i am trying to do is make a multi-select parameter
> > i have one pull down that has the list of values to choose from, and
> > the second pull down thats values are something like
> > customclass.multi(1) etc, and everytime this is populated it will look
> > at the currently selected item from the first pull down and add it to
> > the pulldown of the second.. this works as long as i make arraylist
> > that i use to store the values of the second list to be static , and
> > it works very well and nice, other than because its static, if other
> > users are running the report they are getting the same pulldown, and
> > the next time the user runs the report they get the same problem..
> >
> > just wondering if anybody has any suggestions..
> >
> > i'm thinking of a workaround on using it as static, but maybe making a
> > first hidden parameter that is populated by a GUID that is used as a
> > hash in a hashtable for each particular parmeter list.
>
>