Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
strent00
Starting Member
2 Posts |
 Posted - 2006-04-03 : 16:26:09
|
| Here's my first post to the forum, so thanks for listening. I have a rather fancy drilldown report I created using RS 2000. There are two levels of grouping at the summary level. From there the user can drilldown into a detail row. To make it work I placed a table control (detail level) within a list control (summary level), and all this inside another list control (grouping w/i summary level). From within Report Designer when one clicks on 'View Report', it appears to be working like a charm. However, print preview is another matter. Specifically, I get some odd page breaks and other phenomena. for example, in print preview (or actually printing) the report looks fine for the first few pages. Then comes a page where only group headers print but no detail. (Blank lines appear where the detail should have been.) The page after that is just the opposite: it displays the detail that was missing from the previous page, but with blank lines where the headers should have been. Also, and it may be a separate issue, it also appears that RS 2000 is trying to outsmart me by trying to KeepTogether my groups, even though KeepTogether is unchecked as a group property.Has anyone experienced any similar problems? Thanks.Relative performance is no substitute for absolute achievement. |
|
|
strent00
Starting Member
2 Posts |
Posted - 2006-04-03 : 17:45:15
|
| Good grief!It turns that out the problem with quirky display results I described was simple to solve. And even us veteran reports services analysts would be wise to keep this, the oldest and easiest mistake possible, in mind, else a lesson in humility such as I just received may follow: Be careful whenever you add a control (any control) to a report design screen. If you happen to nudge the right-hand side of the design area even the teensiest, most 'unnoticeable-est' bit by accident with the control you are dropping onto it, Microsoft will outsmart you and, without warning, assume you wanted the page you are designing to be wider, whether or not you really want it to be, and without regard to your margin settings. The strange results that follow might not appear until many pages into your report. Beware, my friends!SteveRelative performance is no substitute for absolute achievement. |
 |
|
|
|
|
|
|
|
RS 2000 List/Drilldown/Printing Problem