|
|
You're in the
sql server reporting services
group:Problems setting webform Report Viewer control height to 100%
sql server reporting services:
SSRS 2005
I have an ASP.NET app using the Report Viewer control. I would like the Report Viewer control to resize as the browser (web page) is resized. Setting <rsweb:ReportViewer ... Width="100%" ... </rsweb:ReportViewer> controls the width as expected. As the page is made wider, the control resizes. However, when I use <rsweb:ReportViewer ... Height="100%" ... </rsweb:ReportViewer> to do the same for the height of the control, the report content does not appear. The toolbars appear, but the report content does not. I have to do something like <rsweb:ReportViewer ... Height="300px" ... </rsweb:ReportViewer> to get my report content to appear. Is this a known problem? Is there something I am overlooking, like is there another property I need to set to get this to work? I cannot find any other property that looks like it is related to this problem. --
Hello Chris,
This is a XHTML artifact. If you remove the doctype in the asp.net page, it will work. Please remove the line <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> in the asp.net page. Sincerely, Wei Lu Microsoft Online Community Support ================================================== Get notification to my posts through email? Please refer to http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif ications. Note: The MSDN Managed Newsgroup support offering is for non-urgent issues where an initial response from the community or a Microsoft Support Engineer within 1 business day is acceptable. Please note that each follow up response may take approximately 2 business days as the support professional working with you may need further investigation to reach the most efficient resolution. The offering is not appropriate for situations that require urgent, real-time or phone-based interactions or complex project analysis and dump analysis issues. Issues of this nature are best handled working with a dedicated Microsoft Support Engineer by contacting Microsoft Customer Support Services (CSS) at http://msdn.microsoft.com/subscriptions/support/default.aspx. ================================================== (This posting is provided "AS IS", with no warranties, and confers no rights.)
Hello Chris,
How is everything going? Does my suggestion resolve your problem? If you have any feedback, please feel free to let me know. Sincerely, Wei Lu Microsoft Online Community Support
Hi Wei,
[quoted text, click to view] >>This is a XHTML artifact. Can you explain in more detail what you mean? Why is the presence of DOCTYPE causing this behavior in the Report Viewer Control? [quoted text, click to view] >>If you remove the doctype in the asp.net page, it will work. >>Please remove the line <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 >>Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> >>in the asp.net page. Why will this fix the problem? What if any other problems will removing that line of code cause? Thanks! -- Chris, SSSI [quoted text, click to view] "Wei Lu [MSFT]" wrote:
> Hello Chris, > > How is everything going? Does my suggestion resolve your problem? > > If you have any feedback, please feel free to let me know. > > Sincerely, > > Wei Lu > > Microsoft Online Community Support >
Hi Wei,
[quoted text, click to view] >>If you remove the doctype in the asp.net page, it will work. >>Please remove the line <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 >>Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> >>in the asp.net page. Our ASP.NET pages have this line: <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN" "http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd"> Not the one that you mentioned. Also, I removed the line of code above, and it made no difference. The report content still does not appear when Height="100%". Only the Report Viewer Control tool bars appear. The report does not appear in the HTML rendering. However, if I export the report being viewed to PDF format, all report content is rendered. This looks like a bug in the Report Viewer Control. -- Chris, SSSI [quoted text, click to view] "Wei Lu [MSFT]" wrote:
> Hello Chris, > > How is everything going? Does my suggestion resolve your problem? > > If you have any feedback, please feel free to let me know. > > Sincerely, > > Wei Lu > > Microsoft Online Community Support >
Hello Wei,
How you test the page? Would you please try to test on a simple page with only one report viewer control on it? Please remove the line and have the height to "100%" for the report viewer. Sincerely, Wei Lu Microsoft Online Community Support ================================================== Get notification to my posts through email? Please refer to http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif ications. Note: The MSDN Managed Newsgroup support offering is for non-urgent issues where an initial response from the community or a Microsoft Support Engineer within 1 business day is acceptable. Please note that each follow up response may take approximately 2 business days as the support professional working with you may need further investigation to reach the most efficient resolution. The offering is not appropriate for situations that require urgent, real-time or phone-based interactions or complex project analysis and dump analysis issues. Issues of this nature are best handled working with a dedicated Microsoft Support Engineer by contacting Microsoft Customer Support Services (CSS) at http://msdn.microsoft.com/subscriptions/support/default.aspx. ================================================== (This posting is provided "AS IS", with no warranties, and confers no rights.)
I have removed the line
in my case the solution perfectly works thanks Wei andrea [quoted text, click to view] "Wei Lu [MSFT]" wrote:
> Hello Chris, > > This is a XHTML artifact. If you remove the doctype in the asp.net page, it > will work. > > Please remove the line <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 > Transitional//EN" > "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> in the asp.net > page. > > Sincerely, > > Wei Lu > > Microsoft Online Community Support > > ================================================== > > Get notification to my posts through email? Please refer to > http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif > ications. > > Note: The MSDN Managed Newsgroup support offering is for non-urgent issues > where an initial response from the community or a Microsoft Support > Engineer within 1 business day is acceptable. Please note that each follow > up response may take approximately 2 business days as the support > professional working with you may need further investigation to reach the > most efficient resolution. The offering is not appropriate for situations > that require urgent, real-time or phone-based interactions or complex > project analysis and dump analysis issues. Issues of this nature are best > handled working with a dedicated Microsoft Support Engineer by contacting > Microsoft Customer Support Services (CSS) at > http://msdn.microsoft.com/subscriptions/support/default.aspx. > > ================================================== > (This posting is provided "AS IS", with no warranties, and confers no > rights.) > > >
[quoted text, click to view]
>>Would you please try to test on a simple page with only one report viewer control on it?I can, but my application does not have a "simple page with only one report viewer control on it". So even if it works on a simple page that does not solve my problem. How do you propose that I fix this problem in my application? -- Chris -- Chris, SSSI [quoted text, click to view] "Wei Lu [MSFT]" wrote:
> Hello Wei, > > How you test the page? > > Would you please try to test on a simple page with only one report viewer > control on it? > > Please remove the line and have the height to "100%" for the report viewer. > > Sincerely, > > Wei Lu > > Microsoft Online Community Support > > ================================================== > > Get notification to my posts through email? Please refer to > http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif > ications. > > Note: The MSDN Managed Newsgroup support offering is for non-urgent issues > where an initial response from the community or a Microsoft Support > Engineer within 1 business day is acceptable. Please note that each follow > up response may take approximately 2 business days as the support > professional working with you may need further investigation to reach the > most efficient resolution. The offering is not appropriate for situations > that require urgent, real-time or phone-based interactions or complex > project analysis and dump analysis issues. Issues of this nature are best > handled working with a dedicated Microsoft Support Engineer by contacting > Microsoft Customer Support Services (CSS) at > http://msdn.microsoft.com/subscriptions/support/default.aspx. > > ================================================== > (This posting is provided "AS IS", with no warranties, and confers no > rights.) >
Andy62,
What is the nature of your page? Is it ASP.NET 1.0, 1.1 or 2.0? Are you using master pages? (we are). -- Chris -- Chris, SSSI [quoted text, click to view] "andy62" wrote:
> I have removed the line > in my case > the solution perfectly works > thanks Wei > andrea > "Wei Lu [MSFT]" wrote: > > > Hello Chris, > > > > This is a XHTML artifact. If you remove the doctype in the asp.net page, it > > will work. > > > > Please remove the line <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 > > Transitional//EN" > > "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> in the asp.net > > page. > > > > Sincerely, > > > > Wei Lu > > > > Microsoft Online Community Support > > > > ================================================== > > > > Get notification to my posts through email? Please refer to > > http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif > > ications. > > > > Note: The MSDN Managed Newsgroup support offering is for non-urgent issues > > where an initial response from the community or a Microsoft Support > > Engineer within 1 business day is acceptable. Please note that each follow > > up response may take approximately 2 business days as the support > > professional working with you may need further investigation to reach the > > most efficient resolution. The offering is not appropriate for situations > > that require urgent, real-time or phone-based interactions or complex > > project analysis and dump analysis issues. Issues of this nature are best > > handled working with a dedicated Microsoft Support Engineer by contacting > > Microsoft Customer Support Services (CSS) at > > http://msdn.microsoft.com/subscriptions/support/default.aspx. > > > > ================================================== > > (This posting is provided "AS IS", with no warranties, and confers no > > rights.) > > > > > >
Hi Wei,
The good news is I solved my problem. I did have to remove the !DOCTYPE as you suggested. But the problem also was related to the fact that the Report Viewer Control was contained inside a table on the page. And that table had no height specified. Once I set height="100%" on the table, the report content for the Report Viewer Control appeared. I thought that if you do not set a size for an html table, that it will be sized based on its content. Since the Report Viewer Control shows the report pages, I would expect the table to be sized accordingly. Anyway I am not sure I understand why my fix solved the problem, but it did fix it. =================== MORE IMPORTANTLY =================== I had some questions in a earlier pose in this thread that you did not answer. Can you please answer them now? [quoted text, click to view] >>This is a XHTML artifact. Can you explain in more detail what you mean? Why is the presence of DOCTYPE causing this behavior in the Report Viewer Control? [quoted text, click to view] >>If you remove the doctype in the asp.net page, it will work. >>Please remove the line <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 >>Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> >>in the asp.net page. Why does this fix the problem? What, if any, other problems will removing that line of code cause? -- Chris -- Chris, SSSI [quoted text, click to view] "Wei Lu [MSFT]" wrote:
> Hello Wei, > > How you test the page? > > Would you please try to test on a simple page with only one report viewer > control on it? > > Please remove the line and have the height to "100%" for the report viewer. > > Sincerely, > > Wei Lu > > Microsoft Online Community Support > > ================================================== > > Get notification to my posts through email? Please refer to > http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif > ications. > > Note: The MSDN Managed Newsgroup support offering is for non-urgent issues > where an initial response from the community or a Microsoft Support > Engineer within 1 business day is acceptable. Please note that each follow > up response may take approximately 2 business days as the support > professional working with you may need further investigation to reach the > most efficient resolution. The offering is not appropriate for situations > that require urgent, real-time or phone-based interactions or complex > project analysis and dump analysis issues. Issues of this nature are best > handled working with a dedicated Microsoft Support Engineer by contacting > Microsoft Customer Support Services (CSS) at > http://msdn.microsoft.com/subscriptions/support/default.aspx. > > ================================================== > (This posting is provided "AS IS", with no warranties, and confers no > rights.) >
Hello Chris,
I think this is that the Report Viewer Control rendered the HTML code does not matc the XHTML artifact. This issue is a known issue of the Report Viewer Control. I got this workaround from the product team and they do not provide more detailed information on this issue. Anyway, I am glad to discuss more detail on this issue but since this is relate the Report Viewer Control Code, I could not provide more detailed information now. Thank you for your follow up. Sincerely, Wei Lu Microsoft Online Community Support
Hi Chris
excuse for the delay of my answer. 1) Asp.Net 2.0 2) No, I don't use master page! andrea -- andrea tiveron director e-metodi.it rome italy [quoted text, click to view] "Chris G." wrote:
> Andy62, > > What is the nature of your page? Is it ASP.NET 1.0, 1.1 or 2.0? > > Are you using master pages? (we are). > > -- Chris > > -- > Chris, SSSI > > > "andy62" wrote: > > > I have removed the line > > in my case > > the solution perfectly works > > thanks Wei > > andrea > > "Wei Lu [MSFT]" wrote: > > > > > Hello Chris, > > > > > > This is a XHTML artifact. If you remove the doctype in the asp.net page, it > > > will work. > > > > > > Please remove the line <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 > > > Transitional//EN" > > > "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> in the asp.net > > > page. > > > > > > Sincerely, > > > > > > Wei Lu > > > > > > Microsoft Online Community Support > > > > > > ================================================== > > > > > > Get notification to my posts through email? Please refer to > > > http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif > > > ications. > > > > > > Note: The MSDN Managed Newsgroup support offering is for non-urgent issues > > > where an initial response from the community or a Microsoft Support > > > Engineer within 1 business day is acceptable. Please note that each follow > > > up response may take approximately 2 business days as the support > > > professional working with you may need further investigation to reach the > > > most efficient resolution. The offering is not appropriate for situations > > > that require urgent, real-time or phone-based interactions or complex > > > project analysis and dump analysis issues. Issues of this nature are best > > > handled working with a dedicated Microsoft Support Engineer by contacting > > > Microsoft Customer Support Services (CSS) at > > > http://msdn.microsoft.com/subscriptions/support/default.aspx. > > > > > > ================================================== > > > (This posting is provided "AS IS", with no warranties, and confers no > > > rights.) > > > > > > > > >
Don't see what you're looking for? Try a search.
|
June 2004
July 2004
August 2004
September 2004
October 2004
November 2004
December 2004
January 2005
February 2005
March 2005
April 2005
May 2005
June 2005
July 2005
August 2005
September 2005
October 2005
November 2005
December 2005
January 2006
February 2006
March 2006
April 2006
May 2006
June 2006
July 2006
August 2006
September 2006
October 2006
November 2006
December 2006
January 2007
February 2007
March 2007
April 2007
May 2007
June 2007
July 2007
August 2007
September 2007
October 2007
November 2007
| home · blog · groups | Questions? Comments? Contact the dn |