Home General
New Blog Posts: Merging Reports - Part 1 and Part 2

BandsPerRecord

edited January 2002 in General
Hi DM,

i want to to print repeated labels with ColumnTraversal from Left to Right.
BandsPerRecord does not honor this.

The report has two columns with seven rows. But if i use BandsPerRecord RB
is always printing on the first (left) column.


Greetings
Sven Heuer

Comments

  • edited January 2002
    The current report engine can't handle this configuration. We'll have to
    come up with a new report engine to be able to handle this case.


    Cheers,

    Jim Bennett
    Digital Metaphors


  • edited January 2002
    Thank you Jim,

    Do you know any -easy- workaround for this ?
    (I suppose you will not create a new report engine for this case :))

    Greetings
    Sven


  • edited January 2002
    One sledgehammer approach is to generate empty detail bands, and when you
    reach the label position where you want to start printing actual labels, you
    can close the dataset and reopen it. Then the report will begin traversing
    from the first record.


    Cheers,

    Jim Bennett
    Digital Metaphors


  • edited January 2002
    Hello Jim,

    may be my translation is wrong...

    I just want to print 10 labels (14 fitting on one page) with the same
    content on one page (with two columns) always starting from the top.
    I don't wanna start the labels in the middle or so.

    Is this really not possible with the engine? Hey, you have the greatest
    reportengine in the world ;-)

    Greetings
    Sven






  • edited January 2002
    You could disconnect the datapipeline from the report. Set the
    Report.PageLimit to 1, and set Report.Autostop to false. Have a counter so
    that as the detail bands print, you can set the visibility of the detail
    band to false on the 11th detail band. If the datapipeline is open, you can
    connect the dbTexts in the detail band to the datapipeline that isn't
    connected to the report. The datapipeline won't traverse any data, and will
    stay on the first record. The dbTexts will display the first record's data
    that they are connected to.

    If you want to print multiple records, then you'll need to NOT set the
    Report.Pagelimit. You'll have to stop the report with a call to
    Report.PageLimitReached. You'll need to track how many labels you have
    printed, and move to the next record of the datapipeline, so you don't waste
    any labels:)

    Cheers,

    Jim Bennett
    Digital Metaphors


  • edited January 2002
    I ever knew. RB is the best report engine. :))

    Thx a lot

    Greeting
    Sven

This discussion has been closed.