I have created a report that contained a subreport that was databound inside a table but I was getting errors when I export to excel - "Subreports within table/matrix cells are ignored".
So I changed my report to bind the subreport to a list control instead of a table and it exports to excel fine but I now have new issues:
1) When I export to pdf it seems to ignore width and height properties, creating a blank page every other page (because it thinks the list control is wider than the page), and it also overlaps other elements below the list control.
2) I also seems to have lost the paging in the viewer control that is handled by setting the interactive height property.
Are these known limitations of the list control and pdf or do I have something wrong in the way I have set-up the report. I can provide .rdlc file samples if necessary.
Thank you
Lee Whitney
For your first issue, I guess the width of your subreport (in designer) is more than the width of the subreport control in your main report. For example, if you had used 8 inches in your subreport designer and if the width of the subreport control in your main report is only 7 inches, it will be spilled to the next page.
Hopefully this will solve your other issues as well.
Shyam
|||I already made sure that my sub report width is less than the control width, in fact if I use the table control rather than the list control (and the widths for both controls are the same) the table control exports just fine to pdf where the list control does not. The list control seems to add a colspan=2 to the raw html though I don't know why but this seems to be my culprit though I have no idea how to get rs not to render the html in this fashion.Thanks
No comments:
Post a Comment