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

How to close a dbpipeline ?

edited January 2002 in General
After having printed a report, the dbpipeline associated with the report
continue to scan the dataset,
if I close the dataset, the pipeline will open it again...
The only way I found is to commit or rollback the associate transaction
How is it possible to close the report and the pipeline (As the pipeline
have a lot of lookup field, it make the application run very slow )...

Thanks
Didier corbasson

Comments

  • edited January 2002
    Hi Didier,

    The dataset is scanned only when printing or previewing, nothing happens
    with the pipeline after printing.
    You should use another dataset for editing, I can't imagine why to use
    transactions in the context of a report.

    regards,
    Chris Ueberall;
  • edited January 2002
    Hi Chris,

    I use the same dataset for editing and reporting,
    Is it wrong ???


    Regards
    Didier Corbasson
  • edited January 2002
    It's not 'wrong' to use a read/write dataset for both data-aware controls
    and reporting, but it is generally not done because the report traverses the
    data. That means that any open edits would be automatically posted when the
    report started and that data-aware controls would update as the report moves
    through the records. For (at least) these reasons, most developers create a
    special dataset for the report...

    Cheers,

    -
    --
    Tom Ollar
    Digital Metaphors Corporation
This discussion has been closed.