Rick Graves wrote:
You got the step pyramid right.
Cool. It was fun to draw! :)
If doing a sample report is easier for you than
explaining how to do it, that is fine by me -- either
will get me started.
Well, my initial thought was to do a screencast, but as you can't view
them that wouldn't help much would it? ;)
So either make the detail band be the height of the
page, or make a group on the pk of the table with
StartOnNewPage=True.
The other main report I have to do is also a one page
per table row type report. In general, which is the
better way to set those up?
It would seem that making the detail band be the
height of the page would depend on the page length
(consider letter vs. legal vs A4). But making a group
on the pk of the table seems contradictory.
Maybe I could add a startOnNewPage prop to the detail band, but I guess
the best option now is to add a group on the pk, and set it to start
start on new page. I don't see this group as contradictory, but normally
your groups would have the possibility of more than one record. The key
is ending up with a report writer that is flexible enough to handle all
reasonable cases.
Note that you actually have the ability to set the detail band height
using an expression that could take into account the current page
height, but that is more complex than setting the groups, and you
wouldn't see this visually reflected in the designer surface.
--
pkm ~ http://paulmcnett.com
_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-users
