Question on subreports

Right now we have one report with two tables in it. The tables are
populated from two different stored procedures. The two tables contain
detail and summary information respectively.
We call the report from a web app, and users can elect to see detail,
summary, or both.
We pass a parameter to control this, and set the tables visiblity
based on it.
Now, I just realized that each of the stored procedures is going to
execute, even if one or the reports is not visible, and I wondered if I
could set this up so I could keep a procedure from executing if we
weren't going to use it.
I wondered if I could do this by using subreports, and including them
based on a parameter.
I thought I'd ask before I started in on this to see if anybody has
done this already.
TIA,
JimMy understanding is when a table or any other data region item is hidden the
underlying dataset is not executed.
You can try to check it by running the SQL Server Profiler Tool.
Med Bouchenafa
<jhcorey@.yahoo.com> a écrit dans le message de news:
1138307871.859110.33690@.z14g2000cwz.googlegroups.com...
> Right now we have one report with two tables in it. The tables are
> populated from two different stored procedures. The two tables contain
> detail and summary information respectively.
> We call the report from a web app, and users can elect to see detail,
> summary, or both.
> We pass a parameter to control this, and set the tables visiblity
> based on it.
> Now, I just realized that each of the stored procedures is going to
> execute, even if one or the reports is not visible, and I wondered if I
> could set this up so I could keep a procedure from executing if we
> weren't going to use it.
> I wondered if I could do this by using subreports, and including them
> based on a parameter.
> I thought I'd ask before I started in on this to see if anybody has
> done this already.
> TIA,
> Jim
>|||In our situation the procedure it's easy to see because one of the
procedures throws an error depending on the data we pass it. There is
a table that uses the dataset from this procedure, and if we set the
table's visibility property to false based on a report parameter, we
still see the error and the reference to the procedure.
It may be that there is somewhere else the procedure is referenced, so
I'll look some more before changing everything.