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

Joining two pipelines

edited April 2011 in General
I have two stored procedures that return different values from two
different tables. In order to make the reports the customer has
backward compatible, I have to put all the rows from both procedures
into one pipeline. I cannot make one procedure because the procedure
gets too large for firebird to handle and you get the error:

Implementation limit exceeded.
block size exceeds implementation restriction.

That's why there are two procedures (joining them into 1 sql statement
gives you the same error).

Is there a way to:

1) Make two report pipelines and join them into one pipeline for the
report somehow?

2) Make two pipelines and when the report is opened for viewing,
automatically switch the datasource of the fields that no longer exist
in pipeline #1 to pipeline #2?

Comments

  • edited April 2011
    Hi Jeff,

    This is interesting, according to the Firebird faq, using stored
    procedures should help avoid the error you are getting.

    http://www.firebirdfaq.org/faq299/

    Pipelines are not containers, they simply "pipe" data from a dataset to
    a report and they are designed to be used as a single pipeline for a
    single report.

    One option would be to create a report with two subreports (each
    connected to the separate pipelines. This way the first dataset will
    print, followed by the next.

    Another would be to combine the data from both datasets into a single
    in-memory dataset and access that with a single pipeline.


    Regards,

    Nico Cizik
    Digital Metaphors
    http://www.digital-metaphors.com

    Best Regards,

    Nico Cizik
    Digital Metaphors
    http://www.digital-metaphors.com
This discussion has been closed.