Monday, March 26, 2012
Report not exporting full file
thumbnail images in it (it serves as a products catalog). When I export as
a PDF or tif, only half the data is exported so in the case of the PDF it
cant open because it says its corrupt, and in the case of a tif, it will
open, but the 2nd half of the pages are missing. The downloaded files are
half the size they should be and when downloading, it say's its complete
after 25 seconds even though its downloaded half the data.
My setup:
1) When I run the report on my local machine and its using sql server and
the image files are stored on the local machine, the report will export
fine.
2) When I run the report from my local machine, but its calling sql server
on a remote server and the image file's paths are to the remote server the
report runs OK, but only half the data is exported.
3) When I run the report from the remote server only half the data is
exported.
Any ideas on what might be happening here?
--
moondaddy@.nospam.comI forgot to mention, if I export it to excel or a web archive I get the
followoing error msg:
Reporting Services Error
----
--
a.. Exception of type
Microsoft.ReportingServices.ReportRendering.ReportRenderingException was
thrown. (rrRenderingError) Get Online Help
a.. Exception of type
Microsoft.ReportingServices.ReportRendering.ReportRenderingException was
thrown.
a.. Index was outside the bounds of the array.
----
--
Microsoft Reporting Services
Any idea what its refereing to when it says "Index was outside the bounds of
the array."?
moondaddy@.nospam.com
"moondaddy" <moondaddy@.nospam.com> wrote in message
news:%232E93MldEHA.2752@.TK2MSFTNGP12.phx.gbl...
> I'm using RS sp1 and have a report that's 50 pages long and has 1000
> thumbnail images in it (it serves as a products catalog). When I export
as
> a PDF or tif, only half the data is exported so in the case of the PDF it
> cant open because it says its corrupt, and in the case of a tif, it will
> open, but the 2nd half of the pages are missing. The downloaded files are
> half the size they should be and when downloading, it say's its complete
> after 25 seconds even though its downloaded half the data.
> My setup:
> 1) When I run the report on my local machine and its using sql server and
> the image files are stored on the local machine, the report will export
> fine.
> 2) When I run the report from my local machine, but its calling sql
server
> on a remote server and the image file's paths are to the remote server the
> report runs OK, but only half the data is exported.
> 3) When I run the report from the remote server only half the data is
> exported.
> Any ideas on what might be happening here?
> --
> moondaddy@.nospam.com
>|||I had tried to get a report to intentionally abort by throwing an exception in custom code in hopes of being able to not send a subscription if there was no data. Throwing an exception just left me with half a report and no error message just like you described here.
Mike
"moondaddy" wrote:
> I forgot to mention, if I export it to excel or a web archive I get the
> followoing error msg:
> Reporting Services Error
> ----
> --
> a.. Exception of type
> Microsoft.ReportingServices.ReportRendering.ReportRenderingException was
> thrown. (rrRenderingError) Get Online Help
> a.. Exception of type
> Microsoft.ReportingServices.ReportRendering.ReportRenderingException was
> thrown.
> a.. Index was outside the bounds of the array.
> ----
> --
> Microsoft Reporting Services
> Any idea what its refereing to when it says "Index was outside the bounds of
> the array."?
>
> --
> moondaddy@.nospam.com
> "moondaddy" <moondaddy@.nospam.com> wrote in message
> news:%232E93MldEHA.2752@.TK2MSFTNGP12.phx.gbl...
> > I'm using RS sp1 and have a report that's 50 pages long and has 1000
> > thumbnail images in it (it serves as a products catalog). When I export
> as
> > a PDF or tif, only half the data is exported so in the case of the PDF it
> > cant open because it says its corrupt, and in the case of a tif, it will
> > open, but the 2nd half of the pages are missing. The downloaded files are
> > half the size they should be and when downloading, it say's its complete
> > after 25 seconds even though its downloaded half the data.
> >
> > My setup:
> > 1) When I run the report on my local machine and its using sql server and
> > the image files are stored on the local machine, the report will export
> > fine.
> > 2) When I run the report from my local machine, but its calling sql
> server
> > on a remote server and the image file's paths are to the remote server the
> > report runs OK, but only half the data is exported.
> > 3) When I run the report from the remote server only half the data is
> > exported.
> >
> > Any ideas on what might be happening here?
> >
> > --
> > moondaddy@.nospam.com
> >
> >
>
>
Monday, March 12, 2012
report manager parameter BUG
1) upload this report into report manager
2) - RUN THE Report, and notice that the 2nd parameter called
'defaultparam' gets set to the date, and it works.. (all the report
does is show this parameter)
3) - go to the parameter editing section of hte report in report
manager
4) - change something UNRELELATED to defaultparam - for instance the
PROMPT of the firstparameter - dummyparam, and then APPLY
5) - go back to the report - and "defaultparam" nolonger calculates the
date (the default parameter expression in the report)
conclusion, report manager not only updates the parameters you change,
(as it should to give the administrator ability to), it erroneously
updates all the parameters..
also i notice that query based default (foir single value, rather than
name,value) don't show up in report manager as "query based" (and thus also
sucumb to this bug")
<?xml version="1.0" encoding="utf-8"?>
<Report
xmlns="http://schemas.microsoft.com/sqlserver/reporting/2003/10/reportdefini..."xmlns:rd="http://schemas.microsoft.com/SQLServer/reporting/reportdesigner">
<RightMargin>1in</RightMargin>
<Body>
<ReportItems>
<Textbox Name="textbox1">
<Style>
<PaddingLeft>2pt</PaddingLeft>
<PaddingBottom>2pt</PaddingBottom>
<PaddingTop>2pt</PaddingTop>
<PaddingRight>2pt</PaddingRight>
</Style>
<Top>0.125in</Top>
<rd:DefaultName>textbox1</rd:DefaultName>
<Height>0.25in</Height>
<Width>1in</Width>
<CanGrow>true</CanGrow>
<Value>=Parameters!defaultparam.Value</Value>
<Left>0.25in</Left>
</Textbox>
</ReportItems>
<Style />
<Height>2in</Height>
</Body>
<TopMargin>1in</TopMargin>
<Width>6.5in</Width>
<LeftMargin>1in</LeftMargin>
<rd:SnapToGrid>true</rd:SnapToGrid>
<rd:DrawGrid>true</rd:DrawGrid>
<rd:ReportID>ed8d8d8c-443f-4598-82a1-db50fd8cbc9a</rd:ReportÂID>
<BottomMargin>1in</BottomMargin>
<ReportParameters>
<ReportParameter Name="dummyparam">
<DataType>String</DataType>
<AllowBlank>true</AllowBlank>
<Prompt>dummyparameter</Prompt>
</ReportParameter>
<ReportParameter Name="defaultparam">
<DataType>String</DataType>
<DefaultValue>
<Values>
<Value>=Format(DateTime.Now,"d")</Value>
</Values>
</DefaultValue>
<AllowBlank>true</AllowBlank>
<Prompt>defaultparam</Prompt>
</ReportParameter>
<ReportParameter Name="nextparam">
<DataType>String</DataType>
<AllowBlank>true</AllowBlank>
<Prompt>Report_Parameter_2</Prompt>
</ReportParameter>
</ReportParameters>
<Language>en-US</Language>
</Report>please excuse the double posts, i thought i was putting it on a private
newsgroup at msdn subscribers|||This is a known limitation of the report manager report parameter page.
This issue should be fixed in Yukon.
--
-Daniel
This posting is provided "AS IS" with no warranties, and confers no rights.
"Karl Prosser" <laborready.com@.kprosser(backwards)> wrote in message
news:2D74DC06-9039-4576-86DB-01055F1A98A6@.microsoft.com...
> please excuse the double posts, i thought i was putting it on a private
> newsgroup at msdn subscribers|||is there a way to make a 'hidden writeable (not read only) parameter' other
than changing in in report manager (which messes up the other default ones?)
because in report designer you can't make it this way, you can omit the
prompt , but then its hidden but gives you READONLY parameter errors if
trying to set it in the URL..
maybe there is a script that uses the webservice or something?
"Daniel Reib [MSFT]" wrote:
> This is a known limitation of the report manager report parameter page.
> This issue should be fixed in Yukon.
> --
> -Daniel
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
> "Karl Prosser" <laborready.com@.kprosser(backwards)> wrote in message
> news:2D74DC06-9039-4576-86DB-01055F1A98A6@.microsoft.com...
> > please excuse the double posts, i thought i was putting it on a private
> > newsgroup at msdn subscribers
>
>|||There is actually a way to achieve a hidden parameter in SP1 and in the
upcoming SP2 through report designer: specify just at least one blank as
report parameter prompt and publish to the report server.
Note: the parameter will still be prompted in designer preview, but it will
not be prompted in the viewer of report manager.
The next version (RS2005) will have a better solution for managing hidden
parameters (also through the SOAP API and report manager).
--
This posting is provided "AS IS" with no warranties, and confers no rights.
"Karl Prosser" <laborready.com@.kprosser(backwards)> wrote in message
news:1BCA549E-DD3D-4754-A1D1-6077EA3D3243@.microsoft.com...
> is there a way to make a 'hidden writeable (not read only) parameter'
> other
> than changing in in report manager (which messes up the other default
> ones?)
> because in report designer you can't make it this way, you can omit the
> prompt , but then its hidden but gives you READONLY parameter errors if
> trying to set it in the URL..
> maybe there is a script that uses the webservice or something?
>
> "Daniel Reib [MSFT]" wrote:
>> This is a known limitation of the report manager report parameter page.
>> This issue should be fixed in Yukon.
>> --
>> -Daniel
>> This posting is provided "AS IS" with no warranties, and confers no
>> rights.
>>
>> "Karl Prosser" <laborready.com@.kprosser(backwards)> wrote in message
>> news:2D74DC06-9039-4576-86DB-01055F1A98A6@.microsoft.com...
>> > please excuse the double posts, i thought i was putting it on a private
>> > newsgroup at msdn subscribers
>>|||nice.. just a space instead of a blank.. well at least i can control it
completely from the RDL, its a big releif, i think i need to start a site
with Questions and Answers for these bizarre things in RS
"Robert Bruckner [MSFT]" wrote:
> There is actually a way to achieve a hidden parameter in SP1 and in the
> upcoming SP2 through report designer: specify just at least one blank as
> report parameter prompt and publish to the report server.
> Note: the parameter will still be prompted in designer preview, but it will
> not be prompted in the viewer of report manager.
>|||Daniel,
Would there happen to be a published list of 'known limitations' for RS SP1,
or do we just have to figure these things out as we come upon them?
--
Adrian M.
MCP
"Daniel Reib [MSFT]" <danreib@.online.microsoft.com> wrote in message
news:ul5cMEUFFHA.2176@.TK2MSFTNGP15.phx.gbl...
> This is a known limitation of the report manager report parameter page.
> This issue should be fixed in Yukon.
> --
> -Daniel
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
>
> "Karl Prosser" <laborready.com@.kprosser(backwards)> wrote in message
> news:2D74DC06-9039-4576-86DB-01055F1A98A6@.microsoft.com...
>> please excuse the double posts, i thought i was putting it on a private
>> newsgroup at msdn subscribers
>|||Unfortunately, such a site does not exist. We are so busy fixing them (and
adding new ones <g>) that we haven't had time to create something like this.
--
Brian Welcker
Group Program Manager
Microsoft SQL Server Reporting Services
This posting is provided "AS IS" with no warranties, and confers no rights.
"Adrian M." <absolutelynospam@.nodomain_.com> wrote in message
news:eGTLpKcFFHA.1292@.TK2MSFTNGP10.phx.gbl...
> Daniel,
> Would there happen to be a published list of 'known limitations' for RS
> SP1, or do we just have to figure these things out as we come upon them?
> --
> Adrian M.
> MCP
> "Daniel Reib [MSFT]" <danreib@.online.microsoft.com> wrote in message
> news:ul5cMEUFFHA.2176@.TK2MSFTNGP15.phx.gbl...
>> This is a known limitation of the report manager report parameter page.
>> This issue should be fixed in Yukon.
>> --
>> -Daniel
>> This posting is provided "AS IS" with no warranties, and confers no
>> rights.
>>
>> "Karl Prosser" <laborready.com@.kprosser(backwards)> wrote in message
>> news:2D74DC06-9039-4576-86DB-01055F1A98A6@.microsoft.com...
>> please excuse the double posts, i thought i was putting it on a private
>> newsgroup at msdn subscribers
>>
>
Report Manager error
(note it is NOT a domain controller). All worked fine.
Recently, following a restart of the machine, I get the following error:
Access to the path "C:\Program Files\Microsoft SQL Server\MSSQL\Reporting
Services\ReportManager\bin" is denied.
I have read numerous posts on this issue. Some suggest the documented
workaround IF the server is a DC. All other posts don't appear to have been
resolved.
I have granted full control to Everyone for the ReportManager and bin
folders but to no effect.
Has anyone encountered the fix for this issue?
Thanks.For anyone that might have stumbled on to this post... I found the solution -
eventually.
Check out the "Impersonate a client after authentication" local policy. The
local ASPNET account must be included. In my case a domain policy was
overriding the local policy.
Friday, March 9, 2012
report manager - parameter bug
1) upload this report into report manager
2) - RUN THE Report, and notice that the 2nd parameter called
'defaultparam' gets set to the date, and it works.. (all the report
does is show this parameter)
3) - go to the parameter editing section of hte report in report
manager
4) - change something UNRELELATED to defaultparam - for instance the
PROMPT of the firstparameter - dummyparam, and then APPLY
5) - go back to the report - and "defaultparam" nolonger calculates the
date (the default parameter expression in the report)
conclusion, report manager not only updates the parameters you change,
(as it should to give the administrator ability to), it erroneously
updates all the parameters..
<?xml version="1.0" encoding="utf-8"?>
<Report
xmlns="http://schemas.microsoft.com/sqlserver/reporting/2003/10/reportdefinition"
xmlns:rd="http://schemas.microsoft.com/SQLServer/reporting/reportdesigner">
<RightMargin>1in</RightMargin>
<Body>
<ReportItems>
<Textbox Name="textbox1">
<Style>
<PaddingLeft>2pt</PaddingLeft>
<PaddingBottom>2pt</PaddingBottom>
<PaddingTop>2pt</PaddingTop>
<PaddingRight>2pt</PaddingRight>
</Style>
<Top>0.125in</Top>
<rd:DefaultName>textbox1</rd:DefaultName>
<Height>0.25in</Height>
<Width>1in</Width>
<CanGrow>true</CanGrow>
<Value>=Parameters!defaultparam.Value</Value>
<Left>0.25in</Left>
</Textbox>
</ReportItems>
<Style />
<Height>2in</Height>
</Body>
<TopMargin>1in</TopMargin>
<Width>6.5in</Width>
<LeftMargin>1in</LeftMargin>
<rd:SnapToGrid>true</rd:SnapToGrid>
<rd:DrawGrid>true</rd:DrawGrid>
<rd:ReportID>ed8d8d8c-443f-4598-82a1-db50fd8cbc9a</rd:ReportID>
<BottomMargin>1in</BottomMargin>
<ReportParameters>
<ReportParameter Name="dummyparam">
<DataType>String</DataType>
<AllowBlank>true</AllowBlank>
<Prompt>dummyparameter</Prompt>
</ReportParameter>
<ReportParameter Name="defaultparam">
<DataType>String</DataType>
<DefaultValue>
<Values>
<Value>=Format(DateTime.Now,"d")</Value>
</Values>
</DefaultValue>
<AllowBlank>true</AllowBlank>
<Prompt>defaultparam</Prompt>
</ReportParameter>
<ReportParameter Name="nextparam">
<DataType>String</DataType>
<AllowBlank>true</AllowBlank>
<Prompt>Report_Parameter_2</Prompt>
</ReportParameter>
</ReportParameters>
<Language>en-US</Language>
</Report>I will post this on the private newsgroup as a bug...
thanks
--
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
<klumsy@.xtra.co.nz> wrote in message
news:1108605533.668474.147440@.c13g2000cwb.googlegroups.com...
> here is an example of this bug at work.. (i am using RS SP1)
> 1) upload this report into report manager
> 2) - RUN THE Report, and notice that the 2nd parameter called
> 'defaultparam' gets set to the date, and it works.. (all the report
> does is show this parameter)
> 3) - go to the parameter editing section of hte report in report
> manager
> 4) - change something UNRELELATED to defaultparam - for instance the
> PROMPT of the firstparameter - dummyparam, and then APPLY
> 5) - go back to the report - and "defaultparam" nolonger calculates the
> date (the default parameter expression in the report)
> conclusion, report manager not only updates the parameters you change,
> (as it should to give the administrator ability to), it erroneously
> updates all the parameters..
>
> <?xml version="1.0" encoding="utf-8"?>
> <Report
> xmlns="http://schemas.microsoft.com/sqlserver/reporting/2003/10/reportdefinition"
> xmlns:rd="">http://schemas.microsoft.com/SQLServer/reporting/reportdesigner">
> <RightMargin>1in</RightMargin>
> <Body>
> <ReportItems>
> <Textbox Name="textbox1">
> <Style>
> <PaddingLeft>2pt</PaddingLeft>
> <PaddingBottom>2pt</PaddingBottom>
> <PaddingTop>2pt</PaddingTop>
> <PaddingRight>2pt</PaddingRight>
> </Style>
> <Top>0.125in</Top>
> <rd:DefaultName>textbox1</rd:DefaultName>
> <Height>0.25in</Height>
> <Width>1in</Width>
> <CanGrow>true</CanGrow>
> <Value>=Parameters!defaultparam.Value</Value>
> <Left>0.25in</Left>
> </Textbox>
> </ReportItems>
> <Style />
> <Height>2in</Height>
> </Body>
> <TopMargin>1in</TopMargin>
> <Width>6.5in</Width>
> <LeftMargin>1in</LeftMargin>
> <rd:SnapToGrid>true</rd:SnapToGrid>
> <rd:DrawGrid>true</rd:DrawGrid>
> <rd:ReportID>ed8d8d8c-443f-4598-82a1-db50fd8cbc9a</rd:ReportID>
> <BottomMargin>1in</BottomMargin>
> <ReportParameters>
> <ReportParameter Name="dummyparam">
> <DataType>String</DataType>
> <AllowBlank>true</AllowBlank>
> <Prompt>dummyparameter</Prompt>
> </ReportParameter>
> <ReportParameter Name="defaultparam">
> <DataType>String</DataType>
> <DefaultValue>
> <Values>
> <Value>=Format(DateTime.Now,"d")</Value>
> </Values>
> </DefaultValue>
> <AllowBlank>true</AllowBlank>
> <Prompt>defaultparam</Prompt>
> </ReportParameter>
> <ReportParameter Name="nextparam">
> <DataType>String</DataType>
> <AllowBlank>true</AllowBlank>
> <Prompt>Report_Parameter_2</Prompt>
> </ReportParameter>
> </ReportParameters>
> <Language>en-US</Language>
> </Report>
>|||By the way, the bad behaviour was duplicated on my machine...
Wayne Snyder, MCDBA, SQL Server MVP
Mariner, Charlotte, NC
www.mariner-usa.com
(Please respond only to the newsgroups.)
I support the Professional Association of SQL Server (PASS) and it's
community of SQL Server professionals.
www.sqlpass.org
<klumsy@.xtra.co.nz> wrote in message
news:1108605533.668474.147440@.c13g2000cwb.googlegroups.com...
> here is an example of this bug at work.. (i am using RS SP1)
> 1) upload this report into report manager
> 2) - RUN THE Report, and notice that the 2nd parameter called
> 'defaultparam' gets set to the date, and it works.. (all the report
> does is show this parameter)
> 3) - go to the parameter editing section of hte report in report
> manager
> 4) - change something UNRELELATED to defaultparam - for instance the
> PROMPT of the firstparameter - dummyparam, and then APPLY
> 5) - go back to the report - and "defaultparam" nolonger calculates the
> date (the default parameter expression in the report)
> conclusion, report manager not only updates the parameters you change,
> (as it should to give the administrator ability to), it erroneously
> updates all the parameters..
>
> <?xml version="1.0" encoding="utf-8"?>
> <Report
> xmlns="http://schemas.microsoft.com/sqlserver/reporting/2003/10/reportdefinition"
> xmlns:rd="">http://schemas.microsoft.com/SQLServer/reporting/reportdesigner">
> <RightMargin>1in</RightMargin>
> <Body>
> <ReportItems>
> <Textbox Name="textbox1">
> <Style>
> <PaddingLeft>2pt</PaddingLeft>
> <PaddingBottom>2pt</PaddingBottom>
> <PaddingTop>2pt</PaddingTop>
> <PaddingRight>2pt</PaddingRight>
> </Style>
> <Top>0.125in</Top>
> <rd:DefaultName>textbox1</rd:DefaultName>
> <Height>0.25in</Height>
> <Width>1in</Width>
> <CanGrow>true</CanGrow>
> <Value>=Parameters!defaultparam.Value</Value>
> <Left>0.25in</Left>
> </Textbox>
> </ReportItems>
> <Style />
> <Height>2in</Height>
> </Body>
> <TopMargin>1in</TopMargin>
> <Width>6.5in</Width>
> <LeftMargin>1in</LeftMargin>
> <rd:SnapToGrid>true</rd:SnapToGrid>
> <rd:DrawGrid>true</rd:DrawGrid>
> <rd:ReportID>ed8d8d8c-443f-4598-82a1-db50fd8cbc9a</rd:ReportID>
> <BottomMargin>1in</BottomMargin>
> <ReportParameters>
> <ReportParameter Name="dummyparam">
> <DataType>String</DataType>
> <AllowBlank>true</AllowBlank>
> <Prompt>dummyparameter</Prompt>
> </ReportParameter>
> <ReportParameter Name="defaultparam">
> <DataType>String</DataType>
> <DefaultValue>
> <Values>
> <Value>=Format(DateTime.Now,"d")</Value>
> </Values>
> </DefaultValue>
> <AllowBlank>true</AllowBlank>
> <Prompt>defaultparam</Prompt>
> </ReportParameter>
> <ReportParameter Name="nextparam">
> <DataType>String</DataType>
> <AllowBlank>true</AllowBlank>
> <Prompt>Report_Parameter_2</Prompt>
> </ReportParameter>
> </ReportParameters>
> <Language>en-US</Language>
> </Report>
>|||You may be interested in this related thread:
http://msdn.microsoft.com/newsgroups/default.aspx?dg=microsoft.public.sqlserver.reportingsvcs&mid=5d83b939-71ab-47fa-9f85-9d15d90dacb9
Also check my recent posting in that same thread for a possible workaround
on RS 2000 (specifying hidden parameters through report designer).
--
This posting is provided "AS IS" with no warranties, and confers no rights.
"Wayne Snyder" <wayne.nospam.snyder@.mariner-usa.com> wrote in message
news:OEIuxKPFFHA.3284@.TK2MSFTNGP09.phx.gbl...
> By the way, the bad behaviour was duplicated on my machine...
>
> --
> Wayne Snyder, MCDBA, SQL Server MVP
> Mariner, Charlotte, NC
> www.mariner-usa.com
> (Please respond only to the newsgroups.)
> I support the Professional Association of SQL Server (PASS) and it's
> community of SQL Server professionals.
> www.sqlpass.org
> <klumsy@.xtra.co.nz> wrote in message
> news:1108605533.668474.147440@.c13g2000cwb.googlegroups.com...
>> here is an example of this bug at work.. (i am using RS SP1)
>> 1) upload this report into report manager
>> 2) - RUN THE Report, and notice that the 2nd parameter called
>> 'defaultparam' gets set to the date, and it works.. (all the report
>> does is show this parameter)
>> 3) - go to the parameter editing section of hte report in report
>> manager
>> 4) - change something UNRELELATED to defaultparam - for instance the
>> PROMPT of the firstparameter - dummyparam, and then APPLY
>> 5) - go back to the report - and "defaultparam" nolonger calculates the
>> date (the default parameter expression in the report)
>> conclusion, report manager not only updates the parameters you change,
>> (as it should to give the administrator ability to), it erroneously
>> updates all the parameters..
>>
>> <?xml version="1.0" encoding="utf-8"?>
>> <Report
>> xmlns="http://schemas.microsoft.com/sqlserver/reporting/2003/10/reportdefinition"
>> xmlns:rd="">http://schemas.microsoft.com/SQLServer/reporting/reportdesigner">
>> <RightMargin>1in</RightMargin>
>> <Body>
>> <ReportItems>
>> <Textbox Name="textbox1">
>> <Style>
>> <PaddingLeft>2pt</PaddingLeft>
>> <PaddingBottom>2pt</PaddingBottom>
>> <PaddingTop>2pt</PaddingTop>
>> <PaddingRight>2pt</PaddingRight>
>> </Style>
>> <Top>0.125in</Top>
>> <rd:DefaultName>textbox1</rd:DefaultName>
>> <Height>0.25in</Height>
>> <Width>1in</Width>
>> <CanGrow>true</CanGrow>
>> <Value>=Parameters!defaultparam.Value</Value>
>> <Left>0.25in</Left>
>> </Textbox>
>> </ReportItems>
>> <Style />
>> <Height>2in</Height>
>> </Body>
>> <TopMargin>1in</TopMargin>
>> <Width>6.5in</Width>
>> <LeftMargin>1in</LeftMargin>
>> <rd:SnapToGrid>true</rd:SnapToGrid>
>> <rd:DrawGrid>true</rd:DrawGrid>
>> <rd:ReportID>ed8d8d8c-443f-4598-82a1-db50fd8cbc9a</rd:ReportID>
>> <BottomMargin>1in</BottomMargin>
>> <ReportParameters>
>> <ReportParameter Name="dummyparam">
>> <DataType>String</DataType>
>> <AllowBlank>true</AllowBlank>
>> <Prompt>dummyparameter</Prompt>
>> </ReportParameter>
>> <ReportParameter Name="defaultparam">
>> <DataType>String</DataType>
>> <DefaultValue>
>> <Values>
>> <Value>=Format(DateTime.Now,"d")</Value>
>> </Values>
>> </DefaultValue>
>> <AllowBlank>true</AllowBlank>
>> <Prompt>defaultparam</Prompt>
>> </ReportParameter>
>> <ReportParameter Name="nextparam">
>> <DataType>String</DataType>
>> <AllowBlank>true</AllowBlank>
>> <Prompt>Report_Parameter_2</Prompt>
>> </ReportParameter>
>> </ReportParameters>
>> <Language>en-US</Language>
>> </Report>
>
Saturday, February 25, 2012
Report Headers vs Page Headers
Hi, this is probably a simple question but I just can't figure it out. I'm using SQL Server Reporting Services 2005 sp1.
I'm trying to design a report that displays a particular embedded image on the first page, and then a different one on every subsequent page. I.e full, fancy company logo on the first page, and a trimmed down version on every other. In Crystal, I would have simply used the Report Header and Page Header sections to achieve this - easy.
However, in SQL Reporting Services, there is only a Page Header section - therefore whatever I place in the Page Header shows on every page. Now, I know how to stop it displaying on the first page, but I don't know how to display the other image instead.
I read in a support forum that it is possible to do this by "placing report items above or below your data regions" but I can't get it to work.
Grateful for any assistance.
Matt
Hello Matt,
Here's what I did to accomplish this task.
In your 'Page Header' section, place your trimmed down image (you want to display on all pages but the first), and set the PrintOnFirstPage property to False. Then, in the 'Body' section, move everything down enough to place your fancy company image at the top. Now, your fancy logo will show on the first page and none after, and your trimmed image will display on all other pages.
Hope this helps.
Jarret
|||Hello Jarret,
Thanks very much, that was helpful. I think I'm nearly there - one last Q though! Now that the Page Header is set not to print on the first page it leaves a white blank space where it will appear on the other pages. Therefore, the image placed in the 'Body' section appears about 1/3 of the way down the first page. Do you know any way to make it appear at the top - at the same level as the Page Header one?
Thanks again
Matt
|||Here’s another way you could do this:
Remove all the images you created earlier
Change PrintOnFirstPage back to true for the Page Header
In the BackgroudImage.Value property of the Page Header, type this: =IIf(Globals!PageNumber = 1, "Link to image that should show on Page 1", "Link to image that should show on the rest of the pages")
Resize your Page Header section to fit the images.
Unless your fancy and trimmed images are the same height, there will be blank space below the shorter of the two.Since you can’t dynamically change the size of a section, I think that’s as good as you’re going to get.
Hope this helps.
Jarret
|||Thanks - I'll give that a try. SSRS is great, but there are some features which Crystal has had for years which it is sadly lacking
Report Headers vs Page Headers
Hi, this is probably a simple question but I just can't figure it out. I'm using SQL Server Reporting Services 2005 sp1.
I'm trying to design a report that displays a particular embedded image on the first page, and then a different one on every subsequent page. I.e full, fancy company logo on the first page, and a trimmed down version on every other. In Crystal, I would have simply used the Report Header and Page Header sections to achieve this - easy.
However, in SQL Reporting Services, there is only a Page Header section - therefore whatever I place in the Page Header shows on every page. Now, I know how to stop it displaying on the first page, but I don't know how to display the other image instead.
I read in a support forum that it is possible to do this by "placing report items above or below your data regions" but I can't get it to work.
Grateful for any assistance.
Matt
Hello Matt,
Here's what I did to accomplish this task.
In your 'Page Header' section, place your trimmed down image (you want to display on all pages but the first), and set the PrintOnFirstPage property to False. Then, in the 'Body' section, move everything down enough to place your fancy company image at the top. Now, your fancy logo will show on the first page and none after, and your trimmed image will display on all other pages.
Hope this helps.
Jarret
|||Hello Jarret,
Thanks very much, that was helpful. I think I'm nearly there - one last Q though! Now that the Page Header is set not to print on the first page it leaves a white blank space where it will appear on the other pages. Therefore, the image placed in the 'Body' section appears about 1/3 of the way down the first page. Do you know any way to make it appear at the top - at the same level as the Page Header one?
Thanks again
Matt
|||Here’s another way you could do this:
Remove all the images you created earlier
Change PrintOnFirstPage back to true for the Page Header
In the BackgroudImage.Value property of the Page Header, type this: =IIf(Globals!PageNumber = 1, "Link to image that should show on Page 1", "Link to image that should show on the rest of the pages")
Resize your Page Header section to fit the images.
Unless your fancy and trimmed images are the same height, there will be blank space below the shorter of the two.Since you can’t dynamically change the size of a section, I think that’s as good as you’re going to get.
Hope this helps.
Jarret
|||Thanks - I'll give that a try. SSRS is great, but there are some features which Crystal has had for years which it is sadly lacking