jfkrueger119584

Very strange behavior here. When viewing a report in the reportviewer control half of the data on the first page is cut off. The page footer is still there so it is simply skipping a bunch of records in a dataset. When I print the report looks fine, when I view the report directly from the report server it looks fine, when I preview the report in visual studio it looks fine. The only place this happens is when viewing it in the report viewer. IMO this is a very serious bug. Anyone have any ideas



Re: Visual Studio Report Controls ReportViewer Cuts Out Data From Middle of Report

Lisa Nicholls

If it is reproducible and not due to some really bizarre aspect of either your layout or data, or some expression that you've overlooked... sure, it would be a really serious bug <s>. OTOH if this was something that report viewer regularly did, I think a lot of us would have noticed it <g>.

So... not to doubt you, but ... details please. What can you tell us about your data and/or your layout that might help us repro and see the behavior

>L<






Re: Visual Studio Report Controls ReportViewer Cuts Out Data From Middle of Report

jfkrueger

If it were a layout/data issue it would have problems in all viewers, not just the reportviewer control. It looks fine in print preview, from VS 2005, and from the Report Server itself. It HAS to be a reportviewer control issue. Now, I'm not saying that there is no way that this problem is due to how the report is laid out or the data, but if it works in all the other renderers and just not in ReportViewer my inclanation is that it is a report viewer control problem.

Not sure exactly what details you are looking for but here are some:

  • Towards the middle of my report I have a List control that is bound to a dataset.
  • Within that list control are two textboxes that display values from the dataset.
  • This list is used to display a list of comments and dates associated with the document.
  • The report is getting cut of in the middle of this list, and not all the time.
    • If there are a bunch of comments, the list goes on to the next page and works most of the time.
    • For some, it will only display a couple of comments on the first page and then move on to the second page where a bunch of comments are skipped (left off of the first page). In these instances I can see that the first page is shorter than the second based on how much I have to scroll down to see the bottom of the report.
    • The footer is always there, meaning that it is cutting items out of the list, it is not just cutting out the bottom of the report.
    • If I go to print preview, all of the comments are there and none are skipped. If I look at this exact report with the same data through the report server, it renders fine. If I preview the report in Visual Studio, it renders fine. The ONLY place this happens is in the Report Viewer control.

Thanks for taking the time to read and respond to my post.





Re: Visual Studio Report Controls ReportViewer Cuts Out Data From Middle of Report

Lisa Nicholls

>> my inclanation [sic] is that it is a report viewer control problem

And your inclination may indeed be correct <s>.

But since it is not widely seen by other people creating reports, there has to be *some* connection between *some* aspect of your layout and/or your data that is causing the issue to appear.

We need to identify what that is. There is no other way that (a) a bug is going to get corrected and (b) we can figure out what to avoid in the meantime or maybe offer a workaround for your report's requirements.

The only way we can try to help is to repro... and thank you for the details you have offered.

If you are comfortable posting or e-mailing your RDL I'd take a shot at repro'ing with your exact layout, and I would dummy up the data.

Let me just ask a couple more things:

* -- Are you using the winform or the webform version of the control

* -- Does your data have hard line break characters (ie CRs and LFs) in with the comments

* -- if it is the web form version, what doctype are you using in the page (or master page if you're using one)

>L<






Re: Visual Studio Report Controls ReportViewer Cuts Out Data From Middle of Report

jfkrueger

Hello again,

Here are the answers to your questions:

  1. Webforms
  2. That was my first guess too but not as far as I can see. I looked through the data on the offending reports and it all seems valid. Furthermore, if tihs were the case the problem would be reproduced in the Print Preview, Visual Studio, and when viewing through the Report Server URL.
  3. <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">

I have no problem posting the RDL but it would be a pain for anyone to try to mock up with data. I really appreciate you trying to help.

Thanks again.





Re: Visual Studio Report Controls ReportViewer Cuts Out Data From Middle of Report

Lisa Nicholls

Hey -- there's nothing "invalid" about hard line breaks in data <g>. And, no, they wouldn't be treated the same way by the other engines necessarily.

I asked because, to repro, I have to know a bit about how your data is actually constructed (although I don't need your data).

I don't usually find it much of a chore to mock up data -- I have some rules I use to make it easier to do than it might be if I didn't do this all the time <g>. I will post the SELECTs I used if I succeed in doing this.

Realize that the "Report Server URL" you're talking about almost certainly has

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN" >

... rather than the declaration you are using. So, no matter what you think of the fact that both of them are rendering and displaying HTML and that therefore they are equivalent, they are not <sigh>.

I know you don't want to do this normally but... as a test, and before I worry about mocking up data, what happens if you switch your doctype in your ASPX page to exactly what ReportServer is using

>L<

>L<






Re: Visual Studio Report Controls ReportViewer Cuts Out Data From Middle of Report

jfkrueger

Changing the DOCTYPE worked. Thanks.