These 3 posts all address same problem: Basically, have some data, either in
a group of text boxes or in a table and they are ending up on two pages of
the report, when they should only be on one.
Has anyone found a solution?
http://www.microsoft.com/communities/newsgroups/en-us/default.aspx?dg=microsoft.public.sqlserver.reportingsvcs&mid=47aa22ae-f3a2-41bd-9b5b-a233914f7c7d&sloc=en-us
http://www.microsoft.com/communities/newsgroups/en-us/default.aspx?dg=microsoft.public.sqlserver.reportingsvcs&mid=12c7fbc6-1aca-4e3a-9b2f-e15917fb7c22&sloc=en-us
http://www.microsoft.com/communities/newsgroups/en-us/default.aspx?dg=microsoft.public.sqlserver.reportingsvcs&mid=76f3399b-06f1-4438-bd6a-d468578e6e20&sloc=en-usI HAVE FOUND A "DIRTY" WAY TO GET THE GROUPINGS WORKING.
THE TRICK IS TO CREATE NESTED GROUPING TABLES.
For example,
I have a query output with Agent name , client name and client details.
In order to keep them grouped, I create a table with one group, the Agent
(header, no details).
In that group, I create a table with one group, the Client (same as above).
And in that I group I create another table with the Client Details.
I only use details at the lower lever (the client details).
That works.
I don't like it because it makes the report complicated but it works.
"msflinx" wrote:
> These 3 posts all address same problem: Basically, have some data, either in
> a group of text boxes or in a table and they are ending up on two pages of
> the report, when they should only be on one.
> Has anyone found a solution?
> http://www.microsoft.com/communities/newsgroups/en-us/default.aspx?dg=microsoft.public.sqlserver.reportingsvcs&mid=47aa22ae-f3a2-41bd-9b5b-a233914f7c7d&sloc=en-us
> http://www.microsoft.com/communities/newsgroups/en-us/default.aspx?dg=microsoft.public.sqlserver.reportingsvcs&mid=12c7fbc6-1aca-4e3a-9b2f-e15917fb7c22&sloc=en-us
> http://www.microsoft.com/communities/newsgroups/en-us/default.aspx?dg=microsoft.public.sqlserver.reportingsvcs&mid=76f3399b-06f1-4438-bd6a-d468578e6e20&sloc=en-us
>|||Very interesting approach. Should work though and since most of my reports
are only three levels deep, I might try it.
Thanks for you assistance.
"Kyriakos" wrote:
> I HAVE FOUND A "DIRTY" WAY TO GET THE GROUPINGS WORKING.
> THE TRICK IS TO CREATE NESTED GROUPING TABLES.
> For example,
> I have a query output with Agent name , client name and client details.
> In order to keep them grouped, I create a table with one group, the Agent
> (header, no details).
> In that group, I create a table with one group, the Client (same as above).
> And in that I group I create another table with the Client Details.
> I only use details at the lower lever (the client details).
> That works.
> I don't like it because it makes the report complicated but it works.
> "msflinx" wrote:
> > These 3 posts all address same problem: Basically, have some data, either in
> > a group of text boxes or in a table and they are ending up on two pages of
> > the report, when they should only be on one.
> >
> > Has anyone found a solution?
> >
> > http://www.microsoft.com/communities/newsgroups/en-us/default.aspx?dg=microsoft.public.sqlserver.reportingsvcs&mid=47aa22ae-f3a2-41bd-9b5b-a233914f7c7d&sloc=en-us
> >
> > http://www.microsoft.com/communities/newsgroups/en-us/default.aspx?dg=microsoft.public.sqlserver.reportingsvcs&mid=12c7fbc6-1aca-4e3a-9b2f-e15917fb7c22&sloc=en-us
> >
> > http://www.microsoft.com/communities/newsgroups/en-us/default.aspx?dg=microsoft.public.sqlserver.reportingsvcs&mid=76f3399b-06f1-4438-bd6a-d468578e6e20&sloc=en-us
> >
> >
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment