Home End User

printout interrupts with some RTMs - no obvious reason

edited February 2003 in End User
Hi,

I'm using Delphi 5 + Paradox7 DB + RBuilder 5.5. I'm a RB-newbie, please be
kind.
we, and some of our customers had strange things happening while using the
RB.
sometimes, at a certain dataset, the print simply stops. the last dataset on
the report is also printed incompletely (only to a certain point of the text
etc.)
we tried to delete the dataset which seemed to cause the problem.
it didn't solve the problem, the next dataset was printed incompletely, too.
it's only with a few RTMs and certain datasets, we cant figure out why.

any hints are appreciated.

Christian

Comments

  • edited February 2003
    Disconnect the event handlers. Perhaps there is an infinite loop or
    something in your code.

    Then make sure that you have the data you expect. Connect a TDBGrid up to
    the data source that is connected to the report's datapipeline.

    Do not alter the dataset or traverse it as the report is generating.

    Are you using DADE? You can copy the generated SQL by ctrl-click over the
    dataview to view the generated MAGIC SQL and place this in a TQuery on a
    form to view the master detail data, or press the preview icon in the
    dataview to view the data for the dataview without master detail linked
    MAGIC SQL.

    If you could recreate a simple example and send it to us at
    support@digital-metaphors.com we can take a look at it.

    Increase the BLOBS To Cache and BLOB Size settings in the BDE configuration.
    Can you test with any other databases other than Paradox, such as Advantage
    or DBISAM?

    Cheers,

    Jim Bennett
    Digital Metaphors


  • edited February 2003
    We have found similar problems with certain HP Printer drivers.

    Changing to LaserJet 5L or LaserJet Series 2 drivers worked for us.

    Paul.

  • edited February 2003
    Run a memory watch tool, such as Sleuth QA or Automated QA to see if the
    printer driver is leaking resources. This could be one cause of the problem.


    Cheers,

    Jim Bennett
    Digital Metaphors


This discussion has been closed.