ReportViewer Height

Hello,

I try to embed my Reports of Reporting Services to ASP .NET Application. I use ReportViewer component of Visual Studio 2005.
When I try to set Height property to 100% there is no report content shown. I tried to set SizeToReportContent property but there wasn't success.
At the same time when I set Height to any particular value e.g. 400px, everything is OK. But of cousre I can't know particular height for every reports.
Did you have any such problems? Can you help me?

Thank you,Xhtml does not treat percentage height the same way as traditional html. Take a look at www.gotreportviewer.com, FAQ #14.|||I also cannot get SizeToReportContent = True to work on my web form report viewer controls. Is this a bug or are we overlooking something?|||SizeToReportContent has no effect when AsyncRendering = true. If you set AsyncRendering = false, which renders the report contents inline (versus being in an iframe), then SizeToReportContent will work.|||I wrote some javascript to size the report after it was loaded, using the AsyncRendering = true.|||

When I set AsyncRendering=true, I get an error message when the user tries to navigate to the second page of my report: " Page navigation is out of range."

When I set AsyncRendering=false, it works correctly.

I am using a remote report.

|||

korggy wrote:

When I set AsyncRendering=true, I get an error message when the user tries to navigate to the second page of my report: " Page navigation is out of range."

When I set AsyncRendering=false, it works correctly.

I am using a remote report.

I figured out a workaround. See this post.

|||

Would it be possible to post your javascript?

I still get scrollbars even when AsyncRendering=false SizeToReportContent=true

|||

dreadjr wrote:

I wrote some javascript to size the report after it was loaded, using the AsyncRendering = true.

Can you please share that with the rest of us please?

|||

This is the script that I am using. If you resize a window, you then have to refresh the page to resize the viewer, but there is probably a workaround for that, too.

css style

.fullheight{margin-bottom:120px;}

javascript

<script language="JavaScript" type="text/JavaScript">

window.onload=function resize(){

var viewer = document.getElementById("<%=ReportViewer1.ClientID %>");

var htmlheight = document.documentElement.clientHeight;

viewer.style.height = (htmlheight - 120) + "px";

}

</script>

<rsweb:ReportViewer ID="ReportViewer1" runat="server" Font-Names="Verdana" Font-Size="8pt"

ProcessingMode="Remote" Width="100%" CssClass="fullheight">

</rsweb:ReportViewer>

ReportViewer Height

Hello,

I try to embed my Reports of Reporting Services to ASP .NET Application. I use ReportViewer component of Visual Studio 2005.
When I try to set Height property to 100% there is no report content shown. I tried to set SizeToReportContent property but there wasn't success.
At the same time when I set Height to any particular value e.g. 400px, everything is OK. But of cousre I can't know particular height for every reports.
Did you have any such problems? Can you help me?

Thank you,Xhtml does not treat percentage height the same way as traditional html. Take a look at www.gotreportviewer.com, FAQ #14.|||I also cannot get SizeToReportContent = True to work on my web form report viewer controls. Is this a bug or are we overlooking something?|||SizeToReportContent has no effect when AsyncRendering = true. If you set AsyncRendering = false, which renders the report contents inline (versus being in an iframe), then SizeToReportContent will work.|||I wrote some javascript to size the report after it was loaded, using the AsyncRendering = true.|||

When I set AsyncRendering=true, I get an error message when the user tries to navigate to the second page of my report: " Page navigation is out of range."

When I set AsyncRendering=false, it works correctly.

I am using a remote report.

|||

korggy wrote:

When I set AsyncRendering=true, I get an error message when the user tries to navigate to the second page of my report: " Page navigation is out of range."

When I set AsyncRendering=false, it works correctly.

I am using a remote report.

I figured out a workaround. See this post.

|||

Would it be possible to post your javascript?

I still get scrollbars even when AsyncRendering=false SizeToReportContent=true

|||

dreadjr wrote:

I wrote some javascript to size the report after it was loaded, using the AsyncRendering = true.

Can you please share that with the rest of us please?

|||

This is the script that I am using. If you resize a window, you then have to refresh the page to resize the viewer, but there is probably a workaround for that, too.

css style

.fullheight{margin-bottom:120px;}

javascript

<script language="JavaScript" type="text/JavaScript">

window.onload=function resize(){

var viewer = document.getElementById("<%=ReportViewer1.ClientID %>");

var htmlheight = document.documentElement.clientHeight;

viewer.style.height = (htmlheight - 120) + "px";

}

</script>

<rsweb:ReportViewer ID="ReportViewer1" runat="server" Font-Names="Verdana" Font-Size="8pt"

ProcessingMode="Remote" Width="100%" CssClass="fullheight">

</rsweb:ReportViewer>

|||thanks for pointing me in the right direction. I wrote this to get rid of the duplicate scrollbars in async mode.

<body>

<script language="JavaScript" type="text/JavaScript">

window.onload=function RemoveScrollbars()

{

document.getElementById("<%=ReportViewer1.ClientID %>").lastChild.firstChild.style.overflow = "visible";

}

</script>

<form runat="server" action="Report.aspx" >

<rsweb:ReportViewer

ID="ReportViewer1"

runat="server"

ProcessingMode="Remote"

AsyncRendering="false"

SizeToReportContent="true" />

</form>

</body>

I gleened this navagation from the nifty tree view in the IE Developer Toolbar.

works like a charm!

ReportViewer Height

Hello,

I try to embed my Reports of Reporting Services to ASP .NET Application. I use ReportViewer component of Visual Studio 2005.
When I try to set Height property to 100% there is no report content shown. I tried to set SizeToReportContent property but there wasn't success.
At the same time when I set Height to any particular value e.g. 400px, everything is OK. But of cousre I can't know particular height for every reports.
Did you have any such problems? Can you help me?

Thank you,Xhtml does not treat percentage height the same way as traditional html. Take a look at www.gotreportviewer.com, FAQ #14.|||I also cannot get SizeToReportContent = True to work on my web form report viewer controls. Is this a bug or are we overlooking something?|||SizeToReportContent has no effect when AsyncRendering = true. If you set AsyncRendering = false, which renders the report contents inline (versus being in an iframe), then SizeToReportContent will work.|||I wrote some javascript to size the report after it was loaded, using the AsyncRendering = true.|||

When I set AsyncRendering=true, I get an error message when the user tries to navigate to the second page of my report: " Page navigation is out of range."

When I set AsyncRendering=false, it works correctly.

I am using a remote report.

|||

korggy wrote:

When I set AsyncRendering=true, I get an error message when the user tries to navigate to the second page of my report: " Page navigation is out of range."

When I set AsyncRendering=false, it works correctly.

I am using a remote report.

I figured out a workaround. See this post.

|||

Would it be possible to post your javascript?

I still get scrollbars even when AsyncRendering=false SizeToReportContent=true

|||

dreadjr wrote:

I wrote some javascript to size the report after it was loaded, using the AsyncRendering = true.

Can you please share that with the rest of us please?

|||

This is the script that I am using. If you resize a window, you then have to refresh the page to resize the viewer, but there is probably a workaround for that, too.

css style

.fullheight{margin-bottom:120px;}

javascript

<script language="JavaScript" type="text/JavaScript">

window.onload=function resize(){

var viewer = document.getElementById("<%=ReportViewer1.ClientID %>");

var htmlheight = document.documentElement.clientHeight;

viewer.style.height = (htmlheight - 120) + "px";

}

</script>

<rsweb:ReportViewer ID="ReportViewer1" runat="server" Font-Names="Verdana" Font-Size="8pt"

ProcessingMode="Remote" Width="100%" CssClass="fullheight">

</rsweb:ReportViewer>

ReportViewer Height

Hello,

I try to embed my Reports of Reporting Services to ASP .NET Application. I use ReportViewer component of Visual Studio 2005.
When I try to set Height property to 100% there is no report content shown. I tried to set SizeToReportContent property but there wasn't success.
At the same time when I set Height to any particular value e.g. 400px, everything is OK. But of cousre I can't know particular height for every reports.
Did you have any such problems? Can you help me?

Thank you,Xhtml does not treat percentage height the same way as traditional html. Take a look at www.gotreportviewer.com, FAQ #14.|||I also cannot get SizeToReportContent = True to work on my web form report viewer controls. Is this a bug or are we overlooking something?|||SizeToReportContent has no effect when AsyncRendering = true. If you set AsyncRendering = false, which renders the report contents inline (versus being in an iframe), then SizeToReportContent will work.|||I wrote some javascript to size the report after it was loaded, using the AsyncRendering = true.|||

When I set AsyncRendering=true, I get an error message when the user tries to navigate to the second page of my report: " Page navigation is out of range."

When I set AsyncRendering=false, it works correctly.

I am using a remote report.

|||

korggy wrote:

When I set AsyncRendering=true, I get an error message when the user tries to navigate to the second page of my report: " Page navigation is out of range."

When I set AsyncRendering=false, it works correctly.

I am using a remote report.

I figured out a workaround. See this post.

|||

Would it be possible to post your javascript?

I still get scrollbars even when AsyncRendering=false SizeToReportContent=true

|||

dreadjr wrote:

I wrote some javascript to size the report after it was loaded, using the AsyncRendering = true.

Can you please share that with the rest of us please?

|||

This is the script that I am using. If you resize a window, you then have to refresh the page to resize the viewer, but there is probably a workaround for that, too.

css style

.fullheight{margin-bottom:120px;}

javascript

<script language="JavaScript" type="text/JavaScript">

window.onload=function resize(){

var viewer = document.getElementById("<%=ReportViewer1.ClientID %>");

var htmlheight = document.documentElement.clientHeight;

viewer.style.height = (htmlheight - 120) + "px";

}

</script>

<rsweb:ReportViewer ID="ReportViewer1" runat="server" Font-Names="Verdana" Font-Size="8pt"

ProcessingMode="Remote" Width="100%" CssClass="fullheight">

</rsweb:ReportViewer>

ReportViewer Height

Hello,

I try to embed my Reports of Reporting Services to ASP .NET Application. I use ReportViewer component of Visual Studio 2005.
When I try to set Height property to 100% there is no report content shown. I tried to set SizeToReportContent property but there wasn't success.
At the same time when I set Height to any particular value e.g. 400px, everything is OK. But of cousre I can't know particular height for every reports.
Did you have any such problems? Can you help me?

Thank you,Xhtml does not treat percentage height the same way as traditional html. Take a look at www.gotreportviewer.com, FAQ #14.|||I also cannot get SizeToReportContent = True to work on my web form report viewer controls. Is this a bug or are we overlooking something?|||SizeToReportContent has no effect when AsyncRendering = true. If you set AsyncRendering = false, which renders the report contents inline (versus being in an iframe), then SizeToReportContent will work.|||I wrote some javascript to size the report after it was loaded, using the AsyncRendering = true.|||

When I set AsyncRendering=true, I get an error message when the user tries to navigate to the second page of my report: " Page navigation is out of range."

When I set AsyncRendering=false, it works correctly.

I am using a remote report.

|||

korggy wrote:

When I set AsyncRendering=true, I get an error message when the user tries to navigate to the second page of my report: " Page navigation is out of range."

When I set AsyncRendering=false, it works correctly.

I am using a remote report.

I figured out a workaround. See this post.

|||

Would it be possible to post your javascript?

I still get scrollbars even when AsyncRendering=false SizeToReportContent=true

|||

dreadjr wrote:

I wrote some javascript to size the report after it was loaded, using the AsyncRendering = true.

Can you please share that with the rest of us please?

|||

This is the script that I am using. If you resize a window, you then have to refresh the page to resize the viewer, but there is probably a workaround for that, too.

css style

.fullheight{margin-bottom:120px;}

javascript

<scriptlanguage="JavaScript"type="text/JavaScript">

window.onload=function resize(){

var viewer = document.getElementById("<%=ReportViewer1.ClientID %>");

var htmlheight = document.documentElement.clientHeight;

viewer.style.height = (htmlheight - 120) + "px";

}

</script>

<rsweb:ReportViewerID="ReportViewer1"runat="server"Font-Names="Verdana"Font-Size="8pt"

ProcessingMode="Remote"Width="100%"CssClass="fullheight">

</rsweb:ReportViewer>

|||thanks for pointing me in the right direction. I wrote this to get rid of the duplicate scrollbars in async mode.

<body>

<script language="JavaScript" type="text/JavaScript">

window.onload=function RemoveScrollbars()

{

document.getElementById("<%=ReportViewer1.ClientID %>").lastChild.firstChild.style.overflow = "visible";

}

</script>

<form runat="server" action="Report.aspx" >

<rsweb:ReportViewer

ID="ReportViewer1"

runat="server"

ProcessingMode="Remote"

AsyncRendering="false"

SizeToReportContent="true" />

</form>

</body>

I gleened this navagation from the nifty tree view in the IE Developer Toolbar.

works like a charm!

sql

ReportViewer Height

Hello,

I try to embed my Reports of Reporting Services to ASP .NET Application. I use ReportViewer component of Visual Studio 2005.
When I try to set Height property to 100% there is no report content shown. I tried to set SizeToReportContent property but there wasn't success.
At the same time when I set Height to any particular value e.g. 400px, everything is OK. But of cousre I can't know particular height for every reports.
Did you have any such problems? Can you help me?

Thank you,Xhtml does not treat percentage height the same way as traditional html. Take a look at www.gotreportviewer.com, FAQ #14.|||I also cannot get SizeToReportContent = True to work on my web form report viewer controls. Is this a bug or are we overlooking something?|||SizeToReportContent has no effect when AsyncRendering = true. If you set AsyncRendering = false, which renders the report contents inline (versus being in an iframe), then SizeToReportContent will work.|||I wrote some javascript to size the report after it was loaded, using the AsyncRendering = true.|||

When I set AsyncRendering=true, I get an error message when the user tries to navigate to the second page of my report: " Page navigation is out of range."

When I set AsyncRendering=false, it works correctly.

I am using a remote report.

|||

korggy wrote:

When I set AsyncRendering=true, I get an error message when the user tries to navigate to the second page of my report: " Page navigation is out of range."

When I set AsyncRendering=false, it works correctly.

I am using a remote report.

I figured out a workaround. See this post.

|||

Would it be possible to post your javascript?

I still get scrollbars even when AsyncRendering=false SizeToReportContent=true

|||

dreadjr wrote:

I wrote some javascript to size the report after it was loaded, using the AsyncRendering = true.

Can you please share that with the rest of us please?

|||

This is the script that I am using. If you resize a window, you then have to refresh the page to resize the viewer, but there is probably a workaround for that, too.

css style

.fullheight{margin-bottom:120px;}

javascript

<script language="JavaScript" type="text/JavaScript">

window.onload=function resize(){

var viewer = document.getElementById("<%=ReportViewer1.ClientID %>");

var htmlheight = document.documentElement.clientHeight;

viewer.style.height = (htmlheight - 120) + "px";

}

</script>

<rsweb:ReportViewer ID="ReportViewer1" runat="server" Font-Names="Verdana" Font-Size="8pt"

ProcessingMode="Remote" Width="100%" CssClass="fullheight">

</rsweb:ReportViewer>

ReportViewer Height

Hello,

I try to embed my Reports of Reporting Services to ASP .NET Application. I use ReportViewer component of Visual Studio 2005.
When I try to set Height property to 100% there is no report content shown. I tried to set SizeToReportContent property but there wasn't success.
At the same time when I set Height to any particular value e.g. 400px, everything is OK. But of cousre I can't know particular height for every reports.
Did you have any such problems? Can you help me?

Thank you,Xhtml does not treat percentage height the same way as traditional html. Take a look at www.gotreportviewer.com, FAQ #14.|||I also cannot get SizeToReportContent = True to work on my web form report viewer controls. Is this a bug or are we overlooking something?|||SizeToReportContent has no effect when AsyncRendering = true. If you set AsyncRendering = false, which renders the report contents inline (versus being in an iframe), then SizeToReportContent will work.|||I wrote some javascript to size the report after it was loaded, using the AsyncRendering = true.|||

When I set AsyncRendering=true, I get an error message when the user tries to navigate to the second page of my report: " Page navigation is out of range."

When I set AsyncRendering=false, it works correctly.

I am using a remote report.

|||

korggy wrote:

When I set AsyncRendering=true, I get an error message when the user tries to navigate to the second page of my report: " Page navigation is out of range."

When I set AsyncRendering=false, it works correctly.

I am using a remote report.

I figured out a workaround. See this post.

|||

Would it be possible to post your javascript?

I still get scrollbars even when AsyncRendering=false SizeToReportContent=true

|||

dreadjr wrote:

I wrote some javascript to size the report after it was loaded, using the AsyncRendering = true.

Can you please share that with the rest of us please?

|||

This is the script that I am using. If you resize a window, you then have to refresh the page to resize the viewer, but there is probably a workaround for that, too.

css style

.fullheight{margin-bottom:120px;}

javascript

<script language="JavaScript" type="text/JavaScript">

window.onload=function resize(){

var viewer = document.getElementById("<%=ReportViewer1.ClientID %>");

var htmlheight = document.documentElement.clientHeight;

viewer.style.height = (htmlheight - 120) + "px";

}

</script>

<rsweb:ReportViewer ID="ReportViewer1" runat="server" Font-Names="Verdana" Font-Size="8pt"

ProcessingMode="Remote" Width="100%" CssClass="fullheight">

</rsweb:ReportViewer>

ReportViewer formatting

All,
I am having an issue with a fairly standard implementation of the
ReportViewer control in an Asp.net application.
I have several fairly strait forward reports, but am having problems with
one that contains several tightly aligned textboxes. I am using a grid
spacing of '0.0625in'.
When designed in Visual Studio, or when exported to PDF, the report renders
fine. However, when viewed in the ReportViewer, several of the text boxes
have been resized or moved.
I am wondering if there are some best-practices that I could utilize in
designing this report. Is there a grid spacing that renders better?
Any thoughts/suggestions would be appreciated!
Pierson2 differences that I have discovered:
1) ReportViewer does not consistently render textboxes that overlap(even
slightly) it compensates for this by realigning them. Exports do handle
overlaping textboxes.
2) If you use a bordered textbox as a 'checkbox', change the text size to
1pt. ReportViewer increases the textbox size to fit text, even if there is
no text supplied.
Hope this helps someone!
"Pierson C" wrote:
> All,
> I am having an issue with a fairly standard implementation of the
> ReportViewer control in an Asp.net application.
> I have several fairly strait forward reports, but am having problems with
> one that contains several tightly aligned textboxes. I am using a grid
> spacing of '0.0625in'.
> When designed in Visual Studio, or when exported to PDF, the report renders
> fine. However, when viewed in the ReportViewer, several of the text boxes
> have been resized or moved.
> I am wondering if there are some best-practices that I could utilize in
> designing this report. Is there a grid spacing that renders better?
> Any thoughts/suggestions would be appreciated!
> Pierson|||Make sure that none of the textboxes overlap. We don't support overlapping
items in some renderers and will move/resize items if needed.
--
This posting is provided "AS IS" with no warranties, and confers no rights.
"Pierson C" <PiersonC@.discussions.microsoft.com> wrote in message
news:ED575E95-145A-401A-BDBB-82659A24580F@.microsoft.com...
> All,
> I am having an issue with a fairly standard implementation of the
> ReportViewer control in an Asp.net application.
> I have several fairly strait forward reports, but am having problems with
> one that contains several tightly aligned textboxes. I am using a grid
> spacing of '0.0625in'.
> When designed in Visual Studio, or when exported to PDF, the report
> renders
> fine. However, when viewed in the ReportViewer, several of the text boxes
> have been resized or moved.
> I am wondering if there are some best-practices that I could utilize in
> designing this report. Is there a grid spacing that renders better?
> Any thoughts/suggestions would be appreciated!
> Pierson

ReportViewer for .NET

I'm a VB6.0 programmer who is new to .Net. I'm having to write a
program in .Net that will call various .rdls in a windows
application. I've done the reports in the Business Intelligence
Studio (2005) pulling from a SQL Server 2005 database, but I don't
have .Net 2005, only Visual Studio 2003 for the VB side. I've read a
lot about using the reportviewer.dll for this, but I can't seem to
find it available for the Visual Studio 2003 or the Express version of
2005. Can someone point me in the right direction?
-wylieThe ReportViewer control assumes the 2.0 Framework and VS2005. It does not
work with 2003. See Chapter 14 of my book for a detailed discussion of this
new control. I also include the ReportViewer control in my (free) INETA
talks and some conference sessions. This is also a good source
http://gotreportviewer.com/.
hth
--
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant, Dad, Grandpa
Microsoft MVP
INETA Speaker
www.betav.com
www.betav.com/blog/billva
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________
Visit www.hitchhikerguides.net to get more information on my latest book:
Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
------
"Wylie" <wylie72@.gmail.com> wrote in message
news:1186409091.881661.58640@.l70g2000hse.googlegroups.com...
> I'm a VB6.0 programmer who is new to .Net. I'm having to write a
> program in .Net that will call various .rdls in a windows
> application. I've done the reports in the Business Intelligence
> Studio (2005) pulling from a SQL Server 2005 database, but I don't
> have .Net 2005, only Visual Studio 2003 for the VB side. I've read a
> lot about using the reportviewer.dll for this, but I can't seem to
> find it available for the Visual Studio 2003 or the Express version of
> 2005. Can someone point me in the right direction?
> -wylie
>sql

ReportViewer control doesn't accept Parameters

Hello,
I have developed a web application that uses ReportViewer Web control
supplied with VS 2005 RTM version. The ReportViewer control uses
Network credentials to connect to a remote SQL 2005 server to get the
reports. It works fine for reports that doesn't use any parameters.
But, for the reports that accepts parameters, the reportviewer control
doesn't seem to read the Parameters selected from the drop-down box.
When I click on the "ViewReport" button the report just reloads with
the initial/default parameter. Can someone please advise if I'm missing
anything here?
PS: All the other options of the control works fine (ie., export,
refresh, page navigation, subreports, document map, etc).I have the same problem so we must both be missing something.
Chris
"Raghu" wrote:
> Hello,
> I have developed a web application that uses ReportViewer Web control
> supplied with VS 2005 RTM version. The ReportViewer control uses
> Network credentials to connect to a remote SQL 2005 server to get the
> reports. It works fine for reports that doesn't use any parameters.
> But, for the reports that accepts parameters, the reportviewer control
> doesn't seem to read the Parameters selected from the drop-down box.
> When I click on the "ViewReport" button the report just reloads with
> the initial/default parameter. Can someone please advise if I'm missing
> anything here?
> PS: All the other options of the control works fine (ie., export,
> refresh, page navigation, subreports, document map, etc).
>|||Hey Ragu, I think I've figured it out.
I was setting the network credentials on each page load instead of the first
time the page was loaded.
I had a look at the ReportViewer code through .NET Reflector and found some
code that indicated that parameter values where not read when the credentials
changed.
Chris
"Raghu" wrote:
> Hello,
> I have developed a web application that uses ReportViewer Web control
> supplied with VS 2005 RTM version. The ReportViewer control uses
> Network credentials to connect to a remote SQL 2005 server to get the
> reports. It works fine for reports that doesn't use any parameters.
> But, for the reports that accepts parameters, the reportviewer control
> doesn't seem to read the Parameters selected from the drop-down box.
> When I click on the "ViewReport" button the report just reloads with
> the initial/default parameter. Can someone please advise if I'm missing
> anything here?
> PS: All the other options of the control works fine (ie., export,
> refresh, page navigation, subreports, document map, etc).
>

ReportViewer and Firefox

Running into a weird problem and wanted to see if anyone else had run into it before. I developed a simple web application using the ReportViewer component with an rdlc report. When I run the project through the development web server in VS, everything looks ok in both Firefox and IE 7. I then deployed the app to a test IIS 6 machine. Looks ok in IE 7, but in Firefox (2.0.0.6, the same one I viewed the test with), the data is all compressed to the left and isn't really readable. Exporting the report (PDF or Excel) looks fine. Anyone have any ideas?

I've run into the same problem.

FireFox seems to have issues with all the nesting in the table structure. I've seen a post about adding a blank textbox in the header set to the width of the report as a fix, haven't had a chance to try it out yet......

Burl

|||

Well, the weird thing, like I said, is that the same application on the dev server in VS 2005 runs just fine in Firefox. It's just when it goes to a test "production" IIS 6 box that it starts acting weird.

|||

Found this post, have to try it out later....

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=83322&SiteID=1

Burl

|||

Setting the page header to can't shrink or grow seems to have worked for me. Still strange that it doesn't show problems in both instances.

|||

Hi!

Have you seen this link?:http://msdn2.microsoft.com/en-us/library/ms156511.aspx

Cheers,

ReportViewer and Click through links

I am creating a .Net application using the ReportViewer, which is working fine.
But when I have a report that has a link to another report, upon clicking
the link it takes the new report to full screen.
What I want to happen is for the new report stay in the ReportViewer.
Any ideas?
--
Regards
<<<Bryan Avery>>Ok I just did this and it was kind of a pain. Too me all day to work it out.
1. You need to use 'Jump to URL' instead of the other options.
2. Open Report Viewer project and add the following code:
Private _linktarget As String = "_self"
<Category("HTMLViewer Commands"), Description("Sets rc:linktarget to change
iFrame target")> _
Public Property LinkTarget() As String
Get
Return Me._linktarget
End Get
Set(ByVal Value As String)
Me._linktarget = Value
Me.SetParameter("rc:LinkTarget", Value)
End Set
End Property
3. Recompile and place dll in project bin.
Now the default is _self and you have the option to change the target from
your code.
This solution isn't ideal because you have to use the jump to url which
means more work in creating the url with params, and you may have to hard
code your servername.
--
Message posted via http://www.sqlmonster.com|||Hi Patrick,
Thanks for the quick response, but I'm a little lost to where I should be
entering line 2, could you give me any more pointers please?
--
Regards
<<<Bryan Avery>>
"Patrick P via SQLMonster.com" wrote:
> Ok I just did this and it was kind of a pain. Too me all day to work it out.
> 1. You need to use 'Jump to URL' instead of the other options.
> 2. Open Report Viewer project and add the following code:
> Private _linktarget As String = "_self"
> <Category("HTMLViewer Commands"), Description("Sets rc:linktarget to change
> iFrame target")> _
> Public Property LinkTarget() As String
> Get
> Return Me._linktarget
> End Get
> Set(ByVal Value As String)
> Me._linktarget = Value
> Me.SetParameter("rc:LinkTarget", Value)
> End Set
> End Property
> 3. Recompile and place dll in project bin.
> Now the default is _self and you have the option to change the target from
> your code.
> This solution isn't ideal because you have to use the jump to url which
> means more work in creating the url with params, and you may have to hard
> code your servername.
> --
> Message posted via http://www.sqlmonster.com
>|||No problem. There are a few changes I discovered since the last post, I'll
note them the end here.
You can find the reportviewer project here:
C:\Program Files\Microsoft SQL Server\MSSQL\Reporting Services\Samples\
Applications\ReportViewer\vb
Open the project and open the ReportViewer.vb class file.
in the "Private Member Variables" region add:
Private _linktarget As String = "_self"
in the "Properties" region add the property in the above thread.
Now here is the addition to the above.
in the "Render" region add the following line to the Render sub:
output.WriteAttribute("name", "ifmReport")
You need this when you call the viewer property you created. Compile and
drop in your bin/GAC.
So now in your app you will add the following line:
rvwReport.LinkTarget = "ifmReport"
rvwReport being your declared instance of the object. In this bit of code:
Protected WithEvents rvwReport As
Microsoft.Samples.ReportingServices.ReportViewer
Now the good news is that I discovered that the "Jump to Report" option
works when I do this, which is great because the "Jump to URL" was a real
pain.
I'm assuming you are a VB and not a C# person.
Hope this helps... now I'm off to post more questions.
--
Message posted via http://www.sqlmonster.com|||Good news is that it is working :-)
Bad news is, it is only working in part.
What I mean is that you can display the first report, and a click to the
next report works okay, but on the third click to the third report it goes
back to full screen :-(
--
Regards
<<<Bryan Avery>>
"Patrick P via SQLMonster.com" wrote:
> No problem. There are a few changes I discovered since the last post, I'll
> note them the end here.
> You can find the reportviewer project here:
> C:\Program Files\Microsoft SQL Server\MSSQL\Reporting Services\Samples\
> Applications\ReportViewer\vb
> Open the project and open the ReportViewer.vb class file.
> in the "Private Member Variables" region add:
> Private _linktarget As String = "_self"
> in the "Properties" region add the property in the above thread.
> Now here is the addition to the above.
> in the "Render" region add the following line to the Render sub:
> output.WriteAttribute("name", "ifmReport")
> You need this when you call the viewer property you created. Compile and
> drop in your bin/GAC.
> So now in your app you will add the following line:
> rvwReport.LinkTarget = "ifmReport"
> rvwReport being your declared instance of the object. In this bit of code:
> Protected WithEvents rvwReport As
> Microsoft.Samples.ReportingServices.ReportViewer
> Now the good news is that I discovered that the "Jump to Report" option
> works when I do this, which is great because the "Jump to URL" was a real
> pain.
> I'm assuming you are a VB and not a C# person.
> Hope this helps... now I'm off to post more questions.
> --
> Message posted via http://www.sqlmonster.com
>|||I know, I'm trying to work that out now. So annoying, thought I had it solved.
Seems that when the report goes back to the server it "forgets" the target
and goes back to "_top". :-\ There has to be a config setting on the server
that we can change. So can anyone out there find it?
--
Message posted via http://www.sqlmonster.com|||Thanks for all your effort.
I was wondering if you know how we can control the tool bar that is within
the ReportViewer so we can have external controls controlling the Zoom,
Export, etc.
Is this something you've come across and is it easy to do?
--
Regards
<<<Bryan Avery>>
"Patrick P via SQLMonster.com" wrote:
> I know, I'm trying to work that out now. So annoying, thought I had it solved.
> Seems that when the report goes back to the server it "forgets" the target
> and goes back to "_top". :-\ There has to be a config setting on the server
> that we can change. So can anyone out there find it?
> --
> Message posted via http://www.sqlmonster.com
>

ReportViewer 2005 InValidOperationException

Hi,

I am using VS 2005 and ReportViewer 2005 web control in ASP.NET 2.0 web application. I am building custom page to host reports in web application. The website is running under known NT account that has rights to the remote Reporting Server.

On the page I am using ReportService2005 web service to retrieve the list of available reports on the server and then trying to use ReportViewer control to display the selected report. I can connect to the remote Reporting Server through Web Service fine and able to retrieve all the data. I can also retrieve the report using the web service. However, when I set the URL and Report path in the ReportViewer control I get following error:

Exception: InValidOperationException

Message: Client found response content type of '', but expected 'text/xml'. The request failed with an empty response.

StackTrace: at Microsoft.SqlServer.ReportingServices2005.Execution.RSExecutionConnection.GetSecureMethods()
at Microsoft.SqlServer.ReportingServices2005.Execution.RSExecutionConnection.IsSecureMethod(String methodname)
at Microsoft.SqlServer.ReportingServices2005.Execution.RSExecutionConnection.LoadReport(String Report, String HistoryID)
at Microsoft.Reporting.WebForms.ServerReport.GetExecutionInfo()
at Microsoft.Reporting.WebForms.ServerReport.GetParameters()
at Microsoft.Reporting.WebForms.ParametersArea.GetMetaDataFromReport(Boolean useCurrentValues)
at Microsoft.Reporting.WebForms.ReportViewer.OnPreRender(EventArgs e)

Initially I thought it could be security issue, but I am able to retireve all the data and report using web service. I believe the error is in the way ReportViewer control is trying to access the report. I am using NT authentication for reporting server and ReportViewerCredentials class is a custom class that used Default Net credentials. Below is the sample code I am using:

rvMain.ProcessingMode = ProcessingMode.Remote;

rvMain.ServerReport.ReportServerCredentials = new ReportViewerCredentials();

rvMain.ServerReport.ReportServerUrl = new Uri("http://testserver/reportserver?");

rvMain.ServerReport.ReportPath = "/Test/TestReport";

I have been striggling with this for a week now. I checked all the blogs and nothing matching this. All this works fine if the reporting server is local to the web application. I would appreciate any help on this.

Ashesh S.

hi,maybe this code example can give you help.

1) implements IReportServerCredentials Interface

public class ReportServerCrendential:IReportServerCredentials
{
// access information for remote reportserver
private string _UserID;
private string _PassWord;
private string _DomainName;

public ReportServerCrendential(string UserID,string Password,string Domain)
{
_UserID = UserID;
_PassWord = Password;
_DomainName = Domain;
}
public bool GetFormsCredentials(out System.Net.Cookie cookie, out string username, out string password, out string authority)
{
cookie = null;
username = password = authority = null;
return false;
}
public WindowsIdentity ImpersonationUser
{
get
{
return null;
}
}
// use this credential
public System.Net.ICredentials NetworkCredentials
{
get
{
return new System.Net.NetworkCredential(_UserID, _PassWord, _DomainName);
}
}

}

2) use this instead of rvMain.ServerReport.ReportServerCredentials = new ReportViewerCredentials();

ReportServerCrendential myCredential = new ReportServerCrendential(UserName, password , "");
rvMain.ServerReport.ReportServerCredentials = myCredential;

.....

rvMain.ServerReport.Refresh();

|||

I tried implementing the IReportServerCredentials as shown above to use username, password and domain. Still I get the same error.

Any help will be greatly appreciated, thanks!

|||

Hi Ashesh,

We are experiencing a similar problem. Did you ever resolve this issue?

Thanks,

Rob

|||

Rob,

No, still working on it. The Report Servers are in web farm using Enterprise Edition and the web application that connects to the report server is using the ReportViewer distrubutable from Microsoft site. I am wondering if the enterprise version has something to do with it. To confirm I am going to host the site on Report server and see if it works.

Trying all possible things. If you find anything let me know. I was hoping some Microsoft guys would answer this thread.

|||

Finally I figured out the issue. Since we are using a web farm environment, we go through Virtual IP to connect to the Reporting Server. The Reporting Service web service is able resolve the VIP, but Report Viewer control is not able to handle it. If I use the report server name in the url, the report displays fine in Report Viewer.

There has to be a way to make ReportViewer contorl work in web farm environment. I believe there are some config changes that you need to do to make it work with Virtual IP. Does anybody know what settings I need to do in config file?

ReportViewer 2005 InValidOperationException

Hi,

I am using VS 2005 and ReportViewer 2005 web control in ASP.NET 2.0 web application. I am building custom page to host reports in web application. The website is running under known NT account that has rights to the remote Reporting Server.

On the page I am using ReportService2005 web service to retrieve the list of available reports on the server and then trying to use ReportViewer control to display the selected report. I can connect to the remote Reporting Server through Web Service fine and able to retrieve all the data. I can also retrieve the report using the web service. However, when I set the URL and Report path in the ReportViewer control I get following error:

Exception: InValidOperationException

Message: Client found response content type of '', but expected 'text/xml'. The request failed with an empty response.

StackTrace: at Microsoft.SqlServer.ReportingServices2005.Execution.RSExecutionConnection.GetSecureMethods()
at Microsoft.SqlServer.ReportingServices2005.Execution.RSExecutionConnection.IsSecureMethod(String methodname)
at Microsoft.SqlServer.ReportingServices2005.Execution.RSExecutionConnection.LoadReport(String Report, String HistoryID)
at Microsoft.Reporting.WebForms.ServerReport.GetExecutionInfo()
at Microsoft.Reporting.WebForms.ServerReport.GetParameters()
at Microsoft.Reporting.WebForms.ParametersArea.GetMetaDataFromReport(Boolean useCurrentValues)
at Microsoft.Reporting.WebForms.ReportViewer.OnPreRender(EventArgs e)

Initially I thought it could be security issue, but I am able to retireve all the data and report using web service. I believe the error is in the way ReportViewer control is trying to access the report. I am using NT authentication for reporting server and ReportViewerCredentials class is a custom class that used Default Net credentials. Below is the sample code I am using:

rvMain.ProcessingMode = ProcessingMode.Remote;

rvMain.ServerReport.ReportServerCredentials = new ReportViewerCredentials();

rvMain.ServerReport.ReportServerUrl = new Uri("http://testserver/reportserver?");

rvMain.ServerReport.ReportPath = "/Test/TestReport";

I have been striggling with this for a week now. I checked all the blogs and nothing matching this. All this works fine if the reporting server is local to the web application. I would appreciate any help on this.

Ashesh S.

hi,maybe this code example can give you help.

1) implements IReportServerCredentials Interface

public class ReportServerCrendential:IReportServerCredentials
{
// access information for remote reportserver
private string _UserID;
private string _PassWord;
private string _DomainName;

public ReportServerCrendential(string UserID,string Password,string Domain)
{
_UserID = UserID;
_PassWord = Password;
_DomainName = Domain;
}
public bool GetFormsCredentials(out System.Net.Cookie cookie, out string username, out string password, out string authority)
{
cookie = null;
username = password = authority = null;
return false;
}
public WindowsIdentity ImpersonationUser
{
get
{
return null;
}
}
// use this credential
public System.Net.ICredentials NetworkCredentials
{
get
{
return new System.Net.NetworkCredential(_UserID, _PassWord, _DomainName);
}
}

}

2) use this instead of rvMain.ServerReport.ReportServerCredentials = new ReportViewerCredentials();

ReportServerCrendential myCredential = new ReportServerCrendential(UserName, password , "");
rvMain.ServerReport.ReportServerCredentials = myCredential;

.....

rvMain.ServerReport.Refresh();

|||

I tried implementing the IReportServerCredentials as shown above to use username, password and domain. Still I get the same error.

Any help will be greatly appreciated, thanks!

|||

Hi Ashesh,

We are experiencing a similar problem. Did you ever resolve this issue?

Thanks,

Rob

|||

Rob,

No, still working on it. The Report Servers are in web farm using Enterprise Edition and the web application that connects to the report server is using the ReportViewer distrubutable from Microsoft site. I am wondering if the enterprise version has something to do with it. To confirm I am going to host the site on Report server and see if it works.

Trying all possible things. If you find anything let me know. I was hoping some Microsoft guys would answer this thread.

|||

Finally I figured out the issue. Since we are using a web farm environment, we go through Virtual IP to connect to the Reporting Server. The Reporting Service web service is able resolve the VIP, but Report Viewer control is not able to handle it. If I use the report server name in the url, the report displays fine in Report Viewer.

There has to be a way to make ReportViewer contorl work in web farm environment. I believe there are some config changes that you need to do to make it work with Virtual IP. Does anybody know what settings I need to do in config file?

ReportViewer - problems with deploying

I have a web application that was written in Visual Studio 2005, ASP.Net. I am using ReportViewer and it runs correctly and quickly in "local" setting. I have installed the ReportViewer.exe from my local machine's harddrive onto the web server and copied my web application to the web server. The aspx page opens fine, I see the reportviewer frame, but I do not see my report. I have tried changing the "ServerReport" and "LocalReport" ReportPath to "http://localhost/test" where the RDLC file is located but still no report shows up on the web server.

Could someone please instruct me how to deploy an ASP.Net web site that is using ReportViewer? I have installed, uninstalled and reinstalled the ReportViewer.exe file. I have downloaded it directly from Microsoft and restarted IIS, as I have seen in other posts. I am running out of options that I can try to get this to work, and I'd hate to have to scrap it and start over using tables and repeaters.

Thanks in advance.

Hi,

From your description, it seems that you want to connect to your report which existed on your remote web server, right?

To deploy reports in an Internet application, you can embed the ReportViewer Web server control in a custom Internet-ready application that you create and deploy. The ReportViewer Web server control is included in Visual Studio 2005 and can be distributed freely with your application. You can configure the control to display reports that run on a report server. The connection between your application and the report server is handled by the control, through the Web service programming interface. All authentication and authorization is handled by your application, which connects to the report server through a single, user-trusted connection.

For more information see:http://technet.microsoft.com/en-us/library/ms159272.aspx
More information on deploying see:http://technet.microsoft.com/en-us/library/ms159868.aspx

Thanks.

sql

ReportViewer

Hi,
I'm using Microsoft.Samples.ReportingServices.ReportViewer for
visualization of the my reports in dotnet C# application.
But, my the ReportViewer position in my folder and do not in my report
when i show my dotnet application.
Example:
My RS manager is:
http://maq-100911/Reporting/
My report name is: Prototipo.rdl
My Report correct visualization in RS Manager is:
http://maq-100911/Reporting/Pages/Report.aspx?ItemPath=%2fPrototipo
How do implementation ReportViewer correctly?
I do:
ReportViewer1.ServerUrl = "http://maq-100911/Reporting";
ReportViewer1.ReportPath = "/Prototipo";
Sorry, i'm from Brazi and my English is so so ...
Tks
MercanteYou have only to build ReportViewer sample and insert it in your webform. It
should work.
I didn't understand what you said:
"But, my the ReportViewer position in my folder and do not in my report when
i show my dotnet application"
Se vc quer, pode escrever isso em portugues.
Jaime
"Mercante" <claumerc@.hotmail.com> wrote in message
news:1123277239.233053.298930@.o13g2000cwo.googlegroups.com...
> Hi,
> I'm using Microsoft.Samples.ReportingServices.ReportViewer for
> visualization of the my reports in dotnet C# application.
> But, my the ReportViewer position in my folder and do not in my report
> when i show my dotnet application.
> Example:
> My RS manager is:
> http://maq-100911/Reporting/
> My report name is: Prototipo.rdl
> My Report correct visualization in RS Manager is:
> http://maq-100911/Reporting/Pages/Report.aspx?ItemPath=%2fPrototipo
> How do implementation ReportViewer correctly?
> I do:
> ReportViewer1.ServerUrl = "http://maq-100911/Reporting";
> ReportViewer1.ReportPath = "/Prototipo";
> Sorry, i'm from Brazi and my English is so so ...
> Tks
> Mercante
>sql

ReportViewe needs a connection? Doesn't make sense...

Hi,
I have a VB .NET 2.0 WinForms application that needs to display reports on a
winform's ReportViewer control.
The application project and a separate reports project are under the same
solution.
The report project has its own global connection and datasource object that
is used by the report.
I test the report inside the Visual Studio developing environment report's
view mode and it works ok.
Then I open the form that has the ReportViewer control (in the application
project), and in the designer, I assign the properties and the report to the
ReportViewer control. I run the application... the form displays, and the
ReportViewer displays an error inside saying there's no dataset. Why? The
report has a connection and a dataset and they work when I test it.
So I create a connection and dataset in the application's project like the
ones I have in the report project, but I can't find a way to assign the
dataset to the ReportViewer...
How can I make this work?
Would you please Help me? This is the tip of the iceberg of all the problems
we're having with our reports and RSvcs... Thanks in advance.
Sincerely,
RichardThe report viewer operates in two modes. One is server based, the other is
local mode. In local mode you give it a .rdlc file (which is a renamed .rdl
file) and a tableset. In server mode you just give it the name of the
report, parameters, etc. It has to have been pointed to a server.
If you are doing local mode you have a lot more you have to do. You have to
handle events such as dealing with subreports (this is because you are
responsible when responding to the event to create the dataset for the
subreport). You have to handle drill through, etc etc. If you have a server
around it is much easier. I looked at local mode and decided to stick with
using the server.
If server mode then you need to have the report deployed to a server.
Hope that helps.
--
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Richard" <Richard@.discussions.microsoft.com> wrote in message
news:D962526B-C414-4C5C-91CB-F671A3B529CA@.microsoft.com...
> Hi,
> I have a VB .NET 2.0 WinForms application that needs to display reports on
> a
> winform's ReportViewer control.
> The application project and a separate reports project are under the same
> solution.
> The report project has its own global connection and datasource object
> that
> is used by the report.
> I test the report inside the Visual Studio developing environment report's
> view mode and it works ok.
> Then I open the form that has the ReportViewer control (in the application
> project), and in the designer, I assign the properties and the report to
> the
> ReportViewer control. I run the application... the form displays, and the
> ReportViewer displays an error inside saying there's no dataset. Why? The
> report has a connection and a dataset and they work when I test it.
> So I create a connection and dataset in the application's project like the
> ones I have in the report project, but I can't find a way to assign the
> dataset to the ReportViewer...
> How can I make this work?
> Would you please Help me? This is the tip of the iceberg of all the
> problems
> we're having with our reports and RSvcs... Thanks in advance.
> Sincerely,
> Richard|||Thank you Bruce,
In local mode it needs a tableset? These reports are all based on stored
procedures. Does that mean they need to be rewritten to use tables?
One thing I noticed is the ReportViewer control needs a ReportDataSet
instance for local reports, but I couldn't find a way to convert/create a
ReportDataSet out of the already-existing dataset. How is it supposed to be
done?
Thanks in advance,
Richard
"Bruce L-C [MVP]" wrote:
> The report viewer operates in two modes. One is server based, the other is
> local mode. In local mode you give it a .rdlc file (which is a renamed .rdl
> file) and a tableset. In server mode you just give it the name of the
> report, parameters, etc. It has to have been pointed to a server.
> If you are doing local mode you have a lot more you have to do. You have to
> handle events such as dealing with subreports (this is because you are
> responsible when responding to the event to create the dataset for the
> subreport). You have to handle drill through, etc etc. If you have a server
> around it is much easier. I looked at local mode and decided to stick with
> using the server.
> If server mode then you need to have the report deployed to a server.
>
> Hope that helps.
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "Richard" <Richard@.discussions.microsoft.com> wrote in message
> news:D962526B-C414-4C5C-91CB-F671A3B529CA@.microsoft.com...
> > Hi,
> >
> > I have a VB .NET 2.0 WinForms application that needs to display reports on
> > a
> > winform's ReportViewer control.
> > The application project and a separate reports project are under the same
> > solution.
> > The report project has its own global connection and datasource object
> > that
> > is used by the report.
> > I test the report inside the Visual Studio developing environment report's
> > view mode and it works ok.
> >
> > Then I open the form that has the ReportViewer control (in the application
> > project), and in the designer, I assign the properties and the report to
> > the
> > ReportViewer control. I run the application... the form displays, and the
> > ReportViewer displays an error inside saying there's no dataset. Why? The
> > report has a connection and a dataset and they work when I test it.
> >
> > So I create a connection and dataset in the application's project like the
> > ones I have in the report project, but I can't find a way to assign the
> > dataset to the ReportViewer...
> >
> > How can I make this work?
> >
> > Would you please Help me? This is the tip of the iceberg of all the
> > problems
> > we're having with our reports and RSvcs... Thanks in advance.
> >
> > Sincerely,
> >
> > Richard
>
>|||Should have used the term datatable. Datasets can have multiple datatables.
In local mode you hand the control a rdlc file and the data. If your data is
from a stored procedure you have to call that stored procedure in your code.
It sounds like you have not written any ado.net code (creating datasets,
executing queries etc).
Local mode requires significantly more coding expertise than creating a
report, deploying it to a reportserver. You have to write code to respond to
events. You have to write code to retrieve the data the report is designed
for. You have to write code to retreive the data for the subreport. It is
non-trivial and if you are coming from a background of never having written
ado.net code then you have a big learning curve.
Are you sure you have to use local mode, do you have a reportserver around
that you can use. The control is quite easy to use in server mode (the
report resides on a server and is rendered there).
Bruce Loehle-Conger
"Richard" <Richard@.discussions.microsoft.com> wrote in message
news:C79C33D3-C72E-4BF3-AC1F-31E77DBC743F@.microsoft.com...
> Thank you Bruce,
> In local mode it needs a tableset? These reports are all based on stored
> procedures. Does that mean they need to be rewritten to use tables?
> One thing I noticed is the ReportViewer control needs a ReportDataSet
> instance for local reports, but I couldn't find a way to convert/create a
> ReportDataSet out of the already-existing dataset. How is it supposed to
> be
> done?
> Thanks in advance,
> Richard
> "Bruce L-C [MVP]" wrote:
>> The report viewer operates in two modes. One is server based, the other
>> is
>> local mode. In local mode you give it a .rdlc file (which is a renamed
>> .rdl
>> file) and a tableset. In server mode you just give it the name of the
>> report, parameters, etc. It has to have been pointed to a server.
>> If you are doing local mode you have a lot more you have to do. You have
>> to
>> handle events such as dealing with subreports (this is because you are
>> responsible when responding to the event to create the dataset for the
>> subreport). You have to handle drill through, etc etc. If you have a
>> server
>> around it is much easier. I looked at local mode and decided to stick
>> with
>> using the server.
>> If server mode then you need to have the report deployed to a server.
>>
>> Hope that helps.
>> --
>> Bruce Loehle-Conger
>> MVP SQL Server Reporting Services
>> "Richard" <Richard@.discussions.microsoft.com> wrote in message
>> news:D962526B-C414-4C5C-91CB-F671A3B529CA@.microsoft.com...
>> > Hi,
>> >
>> > I have a VB .NET 2.0 WinForms application that needs to display reports
>> > on
>> > a
>> > winform's ReportViewer control.
>> > The application project and a separate reports project are under the
>> > same
>> > solution.
>> > The report project has its own global connection and datasource object
>> > that
>> > is used by the report.
>> > I test the report inside the Visual Studio developing environment
>> > report's
>> > view mode and it works ok.
>> >
>> > Then I open the form that has the ReportViewer control (in the
>> > application
>> > project), and in the designer, I assign the properties and the report
>> > to
>> > the
>> > ReportViewer control. I run the application... the form displays, and
>> > the
>> > ReportViewer displays an error inside saying there's no dataset. Why?
>> > The
>> > report has a connection and a dataset and they work when I test it.
>> >
>> > So I create a connection and dataset in the application's project like
>> > the
>> > ones I have in the report project, but I can't find a way to assign the
>> > dataset to the ReportViewer...
>> >
>> > How can I make this work?
>> >
>> > Would you please Help me? This is the tip of the iceberg of all the
>> > problems
>> > we're having with our reports and RSvcs... Thanks in advance.
>> >
>> > Sincerely,
>> >
>> > Richard
>>|||Hi Bruce,
Thank you for helping me. Yes I have experience with ADO .NET but I'm a
newbie in Reporting Services and I need to "port" Crystal Reports (that are
working) to RS. So I have been trying to accomplish this using the local
approach, but I understand now that it would be easier to use reports from
the server instead of local reports.
There is a WinForm where the user selects the criteria (parameter values)
for the report and the application needs to pass these parameter values to
the report (w/o using the built-in report's parameter interface). Would you
please tell me how can this be done?
Thank you in advance,
Richard
==="Bruce L-C [MVP]" wrote:
> Should have used the term datatable. Datasets can have multiple datatables.
> In local mode you hand the control a rdlc file and the data. If your data is
> from a stored procedure you have to call that stored procedure in your code.
> It sounds like you have not written any ado.net code (creating datasets,
> executing queries etc).
> Local mode requires significantly more coding expertise than creating a
> report, deploying it to a reportserver. You have to write code to respond to
> events. You have to write code to retrieve the data the report is designed
> for. You have to write code to retreive the data for the subreport. It is
> non-trivial and if you are coming from a background of never having written
> ado.net code then you have a big learning curve.
> Are you sure you have to use local mode, do you have a reportserver around
> that you can use. The control is quite easy to use in server mode (the
> report resides on a server and is rendered there).
> Bruce Loehle-Conger
>
> "Richard" <Richard@.discussions.microsoft.com> wrote in message
> news:C79C33D3-C72E-4BF3-AC1F-31E77DBC743F@.microsoft.com...
> > Thank you Bruce,
> >
> > In local mode it needs a tableset? These reports are all based on stored
> > procedures. Does that mean they need to be rewritten to use tables?
> >
> > One thing I noticed is the ReportViewer control needs a ReportDataSet
> > instance for local reports, but I couldn't find a way to convert/create a
> > ReportDataSet out of the already-existing dataset. How is it supposed to
> > be
> > done?
> >
> > Thanks in advance,
> >
> > Richard
> >
> > "Bruce L-C [MVP]" wrote:
> >
> >> The report viewer operates in two modes. One is server based, the other
> >> is
> >> local mode. In local mode you give it a .rdlc file (which is a renamed
> >> .rdl
> >> file) and a tableset. In server mode you just give it the name of the
> >> report, parameters, etc. It has to have been pointed to a server.
> >>
> >> If you are doing local mode you have a lot more you have to do. You have
> >> to
> >> handle events such as dealing with subreports (this is because you are
> >> responsible when responding to the event to create the dataset for the
> >> subreport). You have to handle drill through, etc etc. If you have a
> >> server
> >> around it is much easier. I looked at local mode and decided to stick
> >> with
> >> using the server.
> >>
> >> If server mode then you need to have the report deployed to a server.
> >>
> >>
> >> Hope that helps.
> >>
> >> --
> >> Bruce Loehle-Conger
> >> MVP SQL Server Reporting Services
> >>
> >> "Richard" <Richard@.discussions.microsoft.com> wrote in message
> >> news:D962526B-C414-4C5C-91CB-F671A3B529CA@.microsoft.com...
> >> > Hi,
> >> >
> >> > I have a VB .NET 2.0 WinForms application that needs to display reports
> >> > on
> >> > a
> >> > winform's ReportViewer control.
> >> > The application project and a separate reports project are under the
> >> > same
> >> > solution.
> >> > The report project has its own global connection and datasource object
> >> > that
> >> > is used by the report.
> >> > I test the report inside the Visual Studio developing environment
> >> > report's
> >> > view mode and it works ok.
> >> >
> >> > Then I open the form that has the ReportViewer control (in the
> >> > application
> >> > project), and in the designer, I assign the properties and the report
> >> > to
> >> > the
> >> > ReportViewer control. I run the application... the form displays, and
> >> > the
> >> > ReportViewer displays an error inside saying there's no dataset. Why?
> >> > The
> >> > report has a connection and a dataset and they work when I test it.
> >> >
> >> > So I create a connection and dataset in the application's project like
> >> > the
> >> > ones I have in the report project, but I can't find a way to assign the
> >> > dataset to the ReportViewer...
> >> >
> >> > How can I make this work?
> >> >
> >> > Would you please Help me? This is the tip of the iceberg of all the
> >> > problems
> >> > we're having with our reports and RSvcs... Thanks in advance.
> >> >
> >> > Sincerely,
> >> >
> >> > Richard
> >>
> >>
> >>
>
>|||You are correct, using in server mode is much easier. First, it is easier to
develop the report using the report designer and previewing it. Next it is
easier to have full functionality (subreports, drill through, etc).
As far as setting the parameters:
http://msdn2.microsoft.com/en-us/library/microsoft.reporting.winforms.reportparameterinfo.aspx
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Richard" <Richard@.discussions.microsoft.com> wrote in message
news:3914427F-67E0-45D1-B5AE-41F8376726A7@.microsoft.com...
> Hi Bruce,
> Thank you for helping me. Yes I have experience with ADO .NET but I'm a
> newbie in Reporting Services and I need to "port" Crystal Reports (that
> are
> working) to RS. So I have been trying to accomplish this using the local
> approach, but I understand now that it would be easier to use reports from
> the server instead of local reports.
> There is a WinForm where the user selects the criteria (parameter values)
> for the report and the application needs to pass these parameter values to
> the report (w/o using the built-in report's parameter interface). Would
> you
> please tell me how can this be done?
> Thank you in advance,
> Richard
> ===> "Bruce L-C [MVP]" wrote:
>> Should have used the term datatable. Datasets can have multiple
>> datatables.
>> In local mode you hand the control a rdlc file and the data. If your data
>> is
>> from a stored procedure you have to call that stored procedure in your
>> code.
>> It sounds like you have not written any ado.net code (creating datasets,
>> executing queries etc).
>> Local mode requires significantly more coding expertise than creating a
>> report, deploying it to a reportserver. You have to write code to respond
>> to
>> events. You have to write code to retrieve the data the report is
>> designed
>> for. You have to write code to retreive the data for the subreport. It is
>> non-trivial and if you are coming from a background of never having
>> written
>> ado.net code then you have a big learning curve.
>> Are you sure you have to use local mode, do you have a reportserver
>> around
>> that you can use. The control is quite easy to use in server mode (the
>> report resides on a server and is rendered there).
>> Bruce Loehle-Conger
>>
>> "Richard" <Richard@.discussions.microsoft.com> wrote in message
>> news:C79C33D3-C72E-4BF3-AC1F-31E77DBC743F@.microsoft.com...
>> > Thank you Bruce,
>> >
>> > In local mode it needs a tableset? These reports are all based on
>> > stored
>> > procedures. Does that mean they need to be rewritten to use tables?
>> >
>> > One thing I noticed is the ReportViewer control needs a ReportDataSet
>> > instance for local reports, but I couldn't find a way to convert/create
>> > a
>> > ReportDataSet out of the already-existing dataset. How is it supposed
>> > to
>> > be
>> > done?
>> >
>> > Thanks in advance,
>> >
>> > Richard
>> >
>> > "Bruce L-C [MVP]" wrote:
>> >
>> >> The report viewer operates in two modes. One is server based, the
>> >> other
>> >> is
>> >> local mode. In local mode you give it a .rdlc file (which is a renamed
>> >> .rdl
>> >> file) and a tableset. In server mode you just give it the name of the
>> >> report, parameters, etc. It has to have been pointed to a server.
>> >>
>> >> If you are doing local mode you have a lot more you have to do. You
>> >> have
>> >> to
>> >> handle events such as dealing with subreports (this is because you are
>> >> responsible when responding to the event to create the dataset for the
>> >> subreport). You have to handle drill through, etc etc. If you have a
>> >> server
>> >> around it is much easier. I looked at local mode and decided to stick
>> >> with
>> >> using the server.
>> >>
>> >> If server mode then you need to have the report deployed to a server.
>> >>
>> >>
>> >> Hope that helps.
>> >>
>> >> --
>> >> Bruce Loehle-Conger
>> >> MVP SQL Server Reporting Services
>> >>
>> >> "Richard" <Richard@.discussions.microsoft.com> wrote in message
>> >> news:D962526B-C414-4C5C-91CB-F671A3B529CA@.microsoft.com...
>> >> > Hi,
>> >> >
>> >> > I have a VB .NET 2.0 WinForms application that needs to display
>> >> > reports
>> >> > on
>> >> > a
>> >> > winform's ReportViewer control.
>> >> > The application project and a separate reports project are under the
>> >> > same
>> >> > solution.
>> >> > The report project has its own global connection and datasource
>> >> > object
>> >> > that
>> >> > is used by the report.
>> >> > I test the report inside the Visual Studio developing environment
>> >> > report's
>> >> > view mode and it works ok.
>> >> >
>> >> > Then I open the form that has the ReportViewer control (in the
>> >> > application
>> >> > project), and in the designer, I assign the properties and the
>> >> > report
>> >> > to
>> >> > the
>> >> > ReportViewer control. I run the application... the form displays,
>> >> > and
>> >> > the
>> >> > ReportViewer displays an error inside saying there's no dataset.
>> >> > Why?
>> >> > The
>> >> > report has a connection and a dataset and they work when I test it.
>> >> >
>> >> > So I create a connection and dataset in the application's project
>> >> > like
>> >> > the
>> >> > ones I have in the report project, but I can't find a way to assign
>> >> > the
>> >> > dataset to the ReportViewer...
>> >> >
>> >> > How can I make this work?
>> >> >
>> >> > Would you please Help me? This is the tip of the iceberg of all the
>> >> > problems
>> >> > we're having with our reports and RSvcs... Thanks in advance.
>> >> >
>> >> > Sincerely,
>> >> >
>> >> > Richard
>> >>
>> >>
>> >>
>>

ReportView control taking long time to Export report

When using Reserved.ReportViewerWebControl.axd control from within a web
application on a web server to export a Reporting Services report in PDF
format takes 5-10 minutes (note same problem no matter what export format
used). The control was incorporated into the web application via Visual
Studio. But when you export the same report using the web interface provided
on the Reporting Services machine it runs in seconds. The web services
machine of course is using the same control but it is on reporting services
web machine, where as the slow application uses the control provided by
Visual Studio which resides on the web box where the application lives. So
why is the ReportViewer control on the application IIS box, so much slower
than the ReportViewer on the Reporting Services IIS box for the same report?
--
If you are looking for SQL Server examples or a free SQL Server DBA
Dashboard tool check out my Website at http://www.sqlserverexamples.comJust to be clear. Are you saying when you use the Report Manager it takes
seconds? And when you use the report viewer web control it takes minutes?
Because below you are saying this: "The web services machine of course is
using the same control but it is on reporting services" This confuses me.
Is it your app on the machine or Report Manager. I don't think Report
Manager is using the control.
Now as far as the 5-10 minutes, are you using the control in local mode or
server mode?
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Greg Larsen" <gregalarsen@.removeit.msn.com> wrote in message
news:85AD0C03-0420-4C4B-A241-C9249A3EE1CD@.microsoft.com...
> When using Reserved.ReportViewerWebControl.axd control from within a web
> application on a web server to export a Reporting Services report in PDF
> format takes 5-10 minutes (note same problem no matter what export format
> used). The control was incorporated into the web application via Visual
> Studio. But when you export the same report using the web interface
> provided
> on the Reporting Services machine it runs in seconds. The web services
> machine of course is using the same control but it is on reporting
> services
> web machine, where as the slow application uses the control provided by
> Visual Studio which resides on the web box where the application lives.
> So
> why is the ReportViewer control on the application IIS box, so much slower
> than the ReportViewer on the Reporting Services IIS box for the same
> report?
> --
> If you are looking for SQL Server examples or a free SQL Server DBA
> Dashboard tool check out my Website at http://www.sqlserverexamples.com

ReportServer as a separate component

Can the ReportServer web services application be installed without installing SQL Server?

Let me explain a little further what I'm trying to do and if I need to take a different path, I'm open to suggestions.

I am going to be using XML files for data input and RDL files to describe the reports themselves. That being said, I am not in need of a database of any kind (and don't want to be required to use one), but I want to take advantage of Microsoft's rendering capabilities. I have looked into the ReportViewer control, but that control doesn't support all of the rendering extensions that ReportServer does (mostly HTML). I know that ReportServer stores its metadata in a database on the local SQL Server, but I didn't know if there was maybe a standalone installation that I could get my hands on that exposed the SOAP API, but didn't require an SQL Server (or any other database for that matter) for it to exist.

Thanks,
Ken

In order to run the Report Server, you do need a SQL Server database engine to be deployed somewhere on your network - not strictly on the local computer.

To get all the rendering capabilities of the report server, you will need to deploy a report server.

If you don't want to use a report server at all, then the ReportViewer control that ships with Visual Studio 2005 is your best bet.

If you don't want to deploy a report server for every instance of your application, you might choose to use a remote report server. In SQL Server 2005, reporting services provides a method for loading a report on the server without saving it in the report server namespace. To do this you use the LoadReportDefinition SOAP API. You'll also need to add any users of your applications to the System User role on the report server, at the system scope (Site Settings in Report Manager, then edit site wide security settings). Your application would then use the LoadReportDefinition method and privision any information needed through the report server execution SOAP endpoint.

Otherwise, you're stuck iinstalling a report server and then choosing either to have a local sql server relational database or a remote one.

-Lukasz

Reports Timeout when MSRS 2005 Applicaiton Pool is restarted

Greetings,

Has anyone else had a problem with MSRS 2005 after restarting the application pool where it takes about 2 minutes to load the main Reports Home page? This is not a problem for the most part, but since the application pool for Reports recycles regulary by default this can be a major problem.

I have searched for, but have not located any documentation that states how the Applicaiton Pool configuration and be modified with regard to MSRS. Additionally the Reporting Services Configuration Manager does not appear to modify options specific to the Applicaiton Pool. I want to know what I can set the Application Pool properties to.

Anyone?

You can modify the application pool properties using IIS manager.|||

Yes, I understand that I can do that.

The problem is that there are not Microsoft recommendations for the ideal application pool configuration. At least, not one that I can find.