I have made a report with multiple groups, when run the report displays just the first group header / footer and detail and will enable you to drill down into the next group which will display group 2 header / footer and detail, from here you can drill down to group 3 header / footer and detail and so on...
is there a way of formatting the borders of a field in the group footer dependant on what is being viewed on screen by the user, eg they will be viewing either group 1 details, group 2 or group 3 etc.
Is it possible to make some kinda of variable that will return true or false dependant on whether someone is viewing a certain group header, then use this variable in the border formatting options for the field i need to format in the group footer?
if someone could give us a clue along with the code that would be great...
thanks
btw... im using crystal v8.5Not sure what you are trying to do
In each group format the field to different borderssql
Showing posts with label group. Show all posts
Showing posts with label group. Show all posts
Thursday, March 29, 2012
Tuesday, March 27, 2012
Field Error
I am getting the following error:
The group expression for the list â'Titleâ' refers to the field â'Title.
Report item expressions can only refer to fields within the current data set
scope or, if inside an aggregate, the specified data set scope.
When I reference the stored procedure in my report, I do not get a field
list. I believe it is because I am trying to build a report that references a
stored procedure using dynamic sql, and I am told that it has to be dynamic
sql by the DBA.
If I am correct in this, question I have is how do I build a report
referencing dynamic sql without getting this error? The stored procedure
works and returns a resultset.You need to manually add the fields to your field list. You can do this by
right clicking with your mouse over the field list.
"Wannabe" wrote:
> I am getting the following error:
> The group expression for the list â'Titleâ' refers to the field â'Title.
> Report item expressions can only refer to fields within the current data set
> scope or, if inside an aggregate, the specified data set scope.
> When I reference the stored procedure in my report, I do not get a field
> list. I believe it is because I am trying to build a report that references a
> stored procedure using dynamic sql, and I am told that it has to be dynamic
> sql by the DBA.
> If I am correct in this, question I have is how do I build a report
> referencing dynamic sql without getting this error? The stored procedure
> works and returns a resultset.
>|||That was easy!!! Thanks a lot...I never would have found that.
"Mike Collins" wrote:
> You need to manually add the fields to your field list. You can do this by
> right clicking with your mouse over the field list.
> "Wannabe" wrote:
> > I am getting the following error:
> >
> > The group expression for the list â'Titleâ' refers to the field â'Title.
> > Report item expressions can only refer to fields within the current data set
> > scope or, if inside an aggregate, the specified data set scope.
> >
> > When I reference the stored procedure in my report, I do not get a field
> > list. I believe it is because I am trying to build a report that references a
> > stored procedure using dynamic sql, and I am told that it has to be dynamic
> > sql by the DBA.
> >
> > If I am correct in this, question I have is how do I build a report
> > referencing dynamic sql without getting this error? The stored procedure
> > works and returns a resultset.
> >
The group expression for the list â'Titleâ' refers to the field â'Title.
Report item expressions can only refer to fields within the current data set
scope or, if inside an aggregate, the specified data set scope.
When I reference the stored procedure in my report, I do not get a field
list. I believe it is because I am trying to build a report that references a
stored procedure using dynamic sql, and I am told that it has to be dynamic
sql by the DBA.
If I am correct in this, question I have is how do I build a report
referencing dynamic sql without getting this error? The stored procedure
works and returns a resultset.You need to manually add the fields to your field list. You can do this by
right clicking with your mouse over the field list.
"Wannabe" wrote:
> I am getting the following error:
> The group expression for the list â'Titleâ' refers to the field â'Title.
> Report item expressions can only refer to fields within the current data set
> scope or, if inside an aggregate, the specified data set scope.
> When I reference the stored procedure in my report, I do not get a field
> list. I believe it is because I am trying to build a report that references a
> stored procedure using dynamic sql, and I am told that it has to be dynamic
> sql by the DBA.
> If I am correct in this, question I have is how do I build a report
> referencing dynamic sql without getting this error? The stored procedure
> works and returns a resultset.
>|||That was easy!!! Thanks a lot...I never would have found that.
"Mike Collins" wrote:
> You need to manually add the fields to your field list. You can do this by
> right clicking with your mouse over the field list.
> "Wannabe" wrote:
> > I am getting the following error:
> >
> > The group expression for the list â'Titleâ' refers to the field â'Title.
> > Report item expressions can only refer to fields within the current data set
> > scope or, if inside an aggregate, the specified data set scope.
> >
> > When I reference the stored procedure in my report, I do not get a field
> > list. I believe it is because I am trying to build a report that references a
> > stored procedure using dynamic sql, and I am told that it has to be dynamic
> > sql by the DBA.
> >
> > If I am correct in this, question I have is how do I build a report
> > referencing dynamic sql without getting this error? The stored procedure
> > works and returns a resultset.
> >
Monday, March 26, 2012
FETCH in Reporting Services
My name is Scott Moore, I am new to this group. I have worked with RS
for the past year on a learn as I go basis. I need to find a good book
for programming RS. I primarily work in C# and know that you can use
code to create a report in RS. Unfortunatly I am someone that needs
assistance in getting started with something, but once I have that
point in the right direction I can expand on that. I hope I am somewhat
helpful to all that are here and that I can learn a lot from everyone.
HAPPY HOLIDAYS! My question is below.
I wrote a query in SQL using a fetch. It works fine when I run it in
query analyzer, but when I try to run it in RS it does not work. I get
the result from the first select query that sets the cursor. I need to
know if there is a way to get past this first select statement and get
the information I am trying to get. Any help would be appreciated.Just a suggestion - find a work around.
Write a stored procedure instead.
Or avoid using cursors at all costs, unless you're using cursor's specific
functionality.
There are better ways to do simple iterations in SQL Server, rather then
using cursors.
"samoore" <samoore30@.gmail.com> wrote in message
news:1135089582.519825.59000@.g47g2000cwa.googlegroups.com...
> My name is Scott Moore, I am new to this group. I have worked with RS
> for the past year on a learn as I go basis. I need to find a good book
> for programming RS. I primarily work in C# and know that you can use
> code to create a report in RS. Unfortunatly I am someone that needs
> assistance in getting started with something, but once I have that
> point in the right direction I can expand on that. I hope I am somewhat
> helpful to all that are here and that I can learn a lot from everyone.
> HAPPY HOLIDAYS! My question is below.
> I wrote a query in SQL using a fetch. It works fine when I run it in
> query analyzer, but when I try to run it in RS it does not work. I get
> the result from the first select query that sets the cursor. I need to
> know if there is a way to get past this first select statement and get
> the information I am trying to get. Any help would be appreciated.
>
for the past year on a learn as I go basis. I need to find a good book
for programming RS. I primarily work in C# and know that you can use
code to create a report in RS. Unfortunatly I am someone that needs
assistance in getting started with something, but once I have that
point in the right direction I can expand on that. I hope I am somewhat
helpful to all that are here and that I can learn a lot from everyone.
HAPPY HOLIDAYS! My question is below.
I wrote a query in SQL using a fetch. It works fine when I run it in
query analyzer, but when I try to run it in RS it does not work. I get
the result from the first select query that sets the cursor. I need to
know if there is a way to get past this first select statement and get
the information I am trying to get. Any help would be appreciated.Just a suggestion - find a work around.
Write a stored procedure instead.
Or avoid using cursors at all costs, unless you're using cursor's specific
functionality.
There are better ways to do simple iterations in SQL Server, rather then
using cursors.
"samoore" <samoore30@.gmail.com> wrote in message
news:1135089582.519825.59000@.g47g2000cwa.googlegroups.com...
> My name is Scott Moore, I am new to this group. I have worked with RS
> for the past year on a learn as I go basis. I need to find a good book
> for programming RS. I primarily work in C# and know that you can use
> code to create a report in RS. Unfortunatly I am someone that needs
> assistance in getting started with something, but once I have that
> point in the right direction I can expand on that. I hope I am somewhat
> helpful to all that are here and that I can learn a lot from everyone.
> HAPPY HOLIDAYS! My question is below.
> I wrote a query in SQL using a fetch. It works fine when I run it in
> query analyzer, but when I try to run it in RS it does not work. I get
> the result from the first select query that sets the cursor. I need to
> know if there is a way to get past this first select statement and get
> the information I am trying to get. Any help would be appreciated.
>
Feeling Stupid - Multi-Column report layout
Hi all,
New poster to the group. I scanned the group and googled this, but haven't
found a solution yet.
I am having problems setting up a multi-colum layout.
In designer, Click Report Menu / "Report properties".
Select "Layout" tab. Set the "Columns:" properties to 2.
The designer shows me a design space with two columns, but only allows me to
edit the contents in the left most column. Understood.
Problem. I drop a table or list in the designer, and when previewed (in
designer or browser after deploy) I don't get multiple columns. Just a
skinny, very tall report.
BOL has only basic references to multi-column reports.
I feel like I am missing something obvious. Any body have any suggestions?
Thanks,
Bret StatehamUnfortunately, multi-column layout is only supported in the 'page-oriented'
renderers (PDF, TIFF, Print).
--
Brian Welcker
Group Program Manager
Microsoft SQL Server Reporting Services
This posting is provided "AS IS" with no warranties, and confers no rights.
"Bret Stateham" <bret.no.spam@.netconnex.com> wrote in message
news:uPgnLgBSFHA.508@.TK2MSFTNGP12.phx.gbl...
> Hi all,
> New poster to the group. I scanned the group and googled this, but
> haven't found a solution yet.
> I am having problems setting up a multi-colum layout.
> In designer, Click Report Menu / "Report properties".
> Select "Layout" tab. Set the "Columns:" properties to 2.
> The designer shows me a design space with two columns, but only allows me
> to edit the contents in the left most column. Understood.
> Problem. I drop a table or list in the designer, and when previewed (in
> designer or browser after deploy) I don't get multiple columns. Just a
> skinny, very tall report.
> BOL has only basic references to multi-column reports.
> I feel like I am missing something obvious. Any body have any
> suggestions?
> Thanks,
> Bret Stateham
>|||Brain,
Thanks much. I guess I shouldn't feel totally stupid because that wasn't
mentioned in BOL, or at least I didn't notice it, but I somehow still feel
like I should have thought of that.
Bret
"Brian Welcker" <bwelcker@.online.microsoft.com> wrote in message
news:uv%23oJvBSFHA.2932@.TK2MSFTNGP09.phx.gbl...
> Unfortunately, multi-column layout is only supported in the
> 'page-oriented' renderers (PDF, TIFF, Print).
> --
> Brian Welcker
> Group Program Manager
> Microsoft SQL Server Reporting Services
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
> "Bret Stateham" <bret.no.spam@.netconnex.com> wrote in message
> news:uPgnLgBSFHA.508@.TK2MSFTNGP12.phx.gbl...
>> Hi all,
>> New poster to the group. I scanned the group and googled this, but
>> haven't found a solution yet.
>> I am having problems setting up a multi-colum layout.
>> In designer, Click Report Menu / "Report properties".
>> Select "Layout" tab. Set the "Columns:" properties to 2.
>> The designer shows me a design space with two columns, but only allows me
>> to edit the contents in the left most column. Understood.
>> Problem. I drop a table or list in the designer, and when previewed (in
>> designer or browser after deploy) I don't get multiple columns. Just a
>> skinny, very tall report.
>> BOL has only basic references to multi-column reports.
>> I feel like I am missing something obvious. Any body have any
>> suggestions?
>> Thanks,
>> Bret Stateham
>|||The issue is that with HTML, there is no fixed page height so wrapping
multiple columns is sort of weird. We introduced "soft" page breaks late in
the cycle in the HTML renderer but didn't get around to adding the
multi-columns.
--
Brian Welcker
Group Program Manager
Microsoft SQL Server Reporting Services
This posting is provided "AS IS" with no warranties, and confers no rights.
"Bret Stateham" <bret.no.spam@.netconnex.com> wrote in message
news:eiK5P%23CSFHA.2356@.TK2MSFTNGP14.phx.gbl...
> Brain,
> Thanks much. I guess I shouldn't feel totally stupid because that wasn't
> mentioned in BOL, or at least I didn't notice it, but I somehow still feel
> like I should have thought of that.
> Bret
> "Brian Welcker" <bwelcker@.online.microsoft.com> wrote in message
> news:uv%23oJvBSFHA.2932@.TK2MSFTNGP09.phx.gbl...
>> Unfortunately, multi-column layout is only supported in the
>> 'page-oriented' renderers (PDF, TIFF, Print).
>> --
>> Brian Welcker
>> Group Program Manager
>> Microsoft SQL Server Reporting Services
>> This posting is provided "AS IS" with no warranties, and confers no
>> rights.
>> "Bret Stateham" <bret.no.spam@.netconnex.com> wrote in message
>> news:uPgnLgBSFHA.508@.TK2MSFTNGP12.phx.gbl...
>> Hi all,
>> New poster to the group. I scanned the group and googled this, but
>> haven't found a solution yet.
>> I am having problems setting up a multi-colum layout.
>> In designer, Click Report Menu / "Report properties".
>> Select "Layout" tab. Set the "Columns:" properties to 2.
>> The designer shows me a design space with two columns, but only allows
>> me to edit the contents in the left most column. Understood.
>> Problem. I drop a table or list in the designer, and when previewed (in
>> designer or browser after deploy) I don't get multiple columns. Just a
>> skinny, very tall report.
>> BOL has only basic references to multi-column reports.
>> I feel like I am missing something obvious. Any body have any
>> suggestions?
>> Thanks,
>> Bret Stateham
>>
>|||Is there anything you have to do to get multiple columns rendered in a PDF
file. I understand not being able to do it in html, but when you convert it
to PDF it still doesn't wrap. Anything special I need to do?
"Brian Welcker" wrote:
> The issue is that with HTML, there is no fixed page height so wrapping
> multiple columns is sort of weird. We introduced "soft" page breaks late in
> the cycle in the HTML renderer but didn't get around to adding the
> multi-columns.
> --
> Brian Welcker
> Group Program Manager
> Microsoft SQL Server Reporting Services
> This posting is provided "AS IS" with no warranties, and confers no rights.
> "Bret Stateham" <bret.no.spam@.netconnex.com> wrote in message
> news:eiK5P%23CSFHA.2356@.TK2MSFTNGP14.phx.gbl...
> > Brain,
> >
> > Thanks much. I guess I shouldn't feel totally stupid because that wasn't
> > mentioned in BOL, or at least I didn't notice it, but I somehow still feel
> > like I should have thought of that.
> >
> > Bret
> > "Brian Welcker" <bwelcker@.online.microsoft.com> wrote in message
> > news:uv%23oJvBSFHA.2932@.TK2MSFTNGP09.phx.gbl...
> >> Unfortunately, multi-column layout is only supported in the
> >> 'page-oriented' renderers (PDF, TIFF, Print).
> >>
> >> --
> >> Brian Welcker
> >> Group Program Manager
> >> Microsoft SQL Server Reporting Services
> >>
> >> This posting is provided "AS IS" with no warranties, and confers no
> >> rights.
> >>
> >> "Bret Stateham" <bret.no.spam@.netconnex.com> wrote in message
> >> news:uPgnLgBSFHA.508@.TK2MSFTNGP12.phx.gbl...
> >> Hi all,
> >>
> >> New poster to the group. I scanned the group and googled this, but
> >> haven't found a solution yet.
> >>
> >> I am having problems setting up a multi-colum layout.
> >>
> >> In designer, Click Report Menu / "Report properties".
> >> Select "Layout" tab. Set the "Columns:" properties to 2.
> >>
> >> The designer shows me a design space with two columns, but only allows
> >> me to edit the contents in the left most column. Understood.
> >>
> >> Problem. I drop a table or list in the designer, and when previewed (in
> >> designer or browser after deploy) I don't get multiple columns. Just a
> >> skinny, very tall report.
> >>
> >> BOL has only basic references to multi-column reports.
> >>
> >> I feel like I am missing something obvious. Any body have any
> >> suggestions?
> >>
> >> Thanks,
> >>
> >> Bret Stateham
> >>
> >>
> >>
> >
> >
>
>
New poster to the group. I scanned the group and googled this, but haven't
found a solution yet.
I am having problems setting up a multi-colum layout.
In designer, Click Report Menu / "Report properties".
Select "Layout" tab. Set the "Columns:" properties to 2.
The designer shows me a design space with two columns, but only allows me to
edit the contents in the left most column. Understood.
Problem. I drop a table or list in the designer, and when previewed (in
designer or browser after deploy) I don't get multiple columns. Just a
skinny, very tall report.
BOL has only basic references to multi-column reports.
I feel like I am missing something obvious. Any body have any suggestions?
Thanks,
Bret StatehamUnfortunately, multi-column layout is only supported in the 'page-oriented'
renderers (PDF, TIFF, Print).
--
Brian Welcker
Group Program Manager
Microsoft SQL Server Reporting Services
This posting is provided "AS IS" with no warranties, and confers no rights.
"Bret Stateham" <bret.no.spam@.netconnex.com> wrote in message
news:uPgnLgBSFHA.508@.TK2MSFTNGP12.phx.gbl...
> Hi all,
> New poster to the group. I scanned the group and googled this, but
> haven't found a solution yet.
> I am having problems setting up a multi-colum layout.
> In designer, Click Report Menu / "Report properties".
> Select "Layout" tab. Set the "Columns:" properties to 2.
> The designer shows me a design space with two columns, but only allows me
> to edit the contents in the left most column. Understood.
> Problem. I drop a table or list in the designer, and when previewed (in
> designer or browser after deploy) I don't get multiple columns. Just a
> skinny, very tall report.
> BOL has only basic references to multi-column reports.
> I feel like I am missing something obvious. Any body have any
> suggestions?
> Thanks,
> Bret Stateham
>|||Brain,
Thanks much. I guess I shouldn't feel totally stupid because that wasn't
mentioned in BOL, or at least I didn't notice it, but I somehow still feel
like I should have thought of that.
Bret
"Brian Welcker" <bwelcker@.online.microsoft.com> wrote in message
news:uv%23oJvBSFHA.2932@.TK2MSFTNGP09.phx.gbl...
> Unfortunately, multi-column layout is only supported in the
> 'page-oriented' renderers (PDF, TIFF, Print).
> --
> Brian Welcker
> Group Program Manager
> Microsoft SQL Server Reporting Services
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
> "Bret Stateham" <bret.no.spam@.netconnex.com> wrote in message
> news:uPgnLgBSFHA.508@.TK2MSFTNGP12.phx.gbl...
>> Hi all,
>> New poster to the group. I scanned the group and googled this, but
>> haven't found a solution yet.
>> I am having problems setting up a multi-colum layout.
>> In designer, Click Report Menu / "Report properties".
>> Select "Layout" tab. Set the "Columns:" properties to 2.
>> The designer shows me a design space with two columns, but only allows me
>> to edit the contents in the left most column. Understood.
>> Problem. I drop a table or list in the designer, and when previewed (in
>> designer or browser after deploy) I don't get multiple columns. Just a
>> skinny, very tall report.
>> BOL has only basic references to multi-column reports.
>> I feel like I am missing something obvious. Any body have any
>> suggestions?
>> Thanks,
>> Bret Stateham
>|||The issue is that with HTML, there is no fixed page height so wrapping
multiple columns is sort of weird. We introduced "soft" page breaks late in
the cycle in the HTML renderer but didn't get around to adding the
multi-columns.
--
Brian Welcker
Group Program Manager
Microsoft SQL Server Reporting Services
This posting is provided "AS IS" with no warranties, and confers no rights.
"Bret Stateham" <bret.no.spam@.netconnex.com> wrote in message
news:eiK5P%23CSFHA.2356@.TK2MSFTNGP14.phx.gbl...
> Brain,
> Thanks much. I guess I shouldn't feel totally stupid because that wasn't
> mentioned in BOL, or at least I didn't notice it, but I somehow still feel
> like I should have thought of that.
> Bret
> "Brian Welcker" <bwelcker@.online.microsoft.com> wrote in message
> news:uv%23oJvBSFHA.2932@.TK2MSFTNGP09.phx.gbl...
>> Unfortunately, multi-column layout is only supported in the
>> 'page-oriented' renderers (PDF, TIFF, Print).
>> --
>> Brian Welcker
>> Group Program Manager
>> Microsoft SQL Server Reporting Services
>> This posting is provided "AS IS" with no warranties, and confers no
>> rights.
>> "Bret Stateham" <bret.no.spam@.netconnex.com> wrote in message
>> news:uPgnLgBSFHA.508@.TK2MSFTNGP12.phx.gbl...
>> Hi all,
>> New poster to the group. I scanned the group and googled this, but
>> haven't found a solution yet.
>> I am having problems setting up a multi-colum layout.
>> In designer, Click Report Menu / "Report properties".
>> Select "Layout" tab. Set the "Columns:" properties to 2.
>> The designer shows me a design space with two columns, but only allows
>> me to edit the contents in the left most column. Understood.
>> Problem. I drop a table or list in the designer, and when previewed (in
>> designer or browser after deploy) I don't get multiple columns. Just a
>> skinny, very tall report.
>> BOL has only basic references to multi-column reports.
>> I feel like I am missing something obvious. Any body have any
>> suggestions?
>> Thanks,
>> Bret Stateham
>>
>|||Is there anything you have to do to get multiple columns rendered in a PDF
file. I understand not being able to do it in html, but when you convert it
to PDF it still doesn't wrap. Anything special I need to do?
"Brian Welcker" wrote:
> The issue is that with HTML, there is no fixed page height so wrapping
> multiple columns is sort of weird. We introduced "soft" page breaks late in
> the cycle in the HTML renderer but didn't get around to adding the
> multi-columns.
> --
> Brian Welcker
> Group Program Manager
> Microsoft SQL Server Reporting Services
> This posting is provided "AS IS" with no warranties, and confers no rights.
> "Bret Stateham" <bret.no.spam@.netconnex.com> wrote in message
> news:eiK5P%23CSFHA.2356@.TK2MSFTNGP14.phx.gbl...
> > Brain,
> >
> > Thanks much. I guess I shouldn't feel totally stupid because that wasn't
> > mentioned in BOL, or at least I didn't notice it, but I somehow still feel
> > like I should have thought of that.
> >
> > Bret
> > "Brian Welcker" <bwelcker@.online.microsoft.com> wrote in message
> > news:uv%23oJvBSFHA.2932@.TK2MSFTNGP09.phx.gbl...
> >> Unfortunately, multi-column layout is only supported in the
> >> 'page-oriented' renderers (PDF, TIFF, Print).
> >>
> >> --
> >> Brian Welcker
> >> Group Program Manager
> >> Microsoft SQL Server Reporting Services
> >>
> >> This posting is provided "AS IS" with no warranties, and confers no
> >> rights.
> >>
> >> "Bret Stateham" <bret.no.spam@.netconnex.com> wrote in message
> >> news:uPgnLgBSFHA.508@.TK2MSFTNGP12.phx.gbl...
> >> Hi all,
> >>
> >> New poster to the group. I scanned the group and googled this, but
> >> haven't found a solution yet.
> >>
> >> I am having problems setting up a multi-colum layout.
> >>
> >> In designer, Click Report Menu / "Report properties".
> >> Select "Layout" tab. Set the "Columns:" properties to 2.
> >>
> >> The designer shows me a design space with two columns, but only allows
> >> me to edit the contents in the left most column. Understood.
> >>
> >> Problem. I drop a table or list in the designer, and when previewed (in
> >> designer or browser after deploy) I don't get multiple columns. Just a
> >> skinny, very tall report.
> >>
> >> BOL has only basic references to multi-column reports.
> >>
> >> I feel like I am missing something obvious. Any body have any
> >> suggestions?
> >>
> >> Thanks,
> >>
> >> Bret Stateham
> >>
> >>
> >>
> >
> >
>
>
Subscribe to:
Posts (Atom)