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

endless loop *ONLY* when printing to printer

edited April 2005 in General
Hi all,
d7Ent, rb7.04, win2kPro, Samsung SCX5112, HP Laserjet 4050, EPSON C80.
I have a simple report that gets data from an RxMemoryTable populated in the
ppReport.BeforePrint event. I also have a master-detail relationship between
RxMemoryTable and another dataset via the dataset's DataSource property (not the
pipeline materDataPipeline/masterfieldlinks capability), where RxMemoryTable is
the master.
The preview works perfectly and i can browse through the pages seeing the whole
data. Even the subsequent print to a PDF printer works OK. But if i print to
*ANY* of the phisical printers in my office i get an infinite loop between pages
0 and -1 (?) in the dialog that says "calculating data from page...".
Sometimes all works ok (no infinite loop) but the printer spits a series of
blank sheet.
BTW, i don't think about a driver problem, 'cause the problem happens only with
this report and on different printers (listed above)
Can anyone help me?
Thanks to all
Gianantonio - ITALY

Comments

  • edited April 2005
    Hi Gianantonio,

    Are you able to print directly, bypassing the preview window? When you
    enter the endless loop, if you pause the program, where in the RBuilder
    source or other source is the application hanging? Try placing a break
    point in the BeforePrint event to be sure it is firing when you expect it
    to. It may be necessary to move this code elsewhere.

    --
    Regards,

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

    Best Regards,

    Nico Cizik
    Digital Metaphors
    http://www.digital-metaphors.com
  • edited April 2005
    Hi Nico, thanks for your quick reply

  • edited April 2005
    Hi Gianantonio,

    Usually when you get different results between the preview and printer, it
    means there is some event code firing (or not firing) that is causing the
    behavior. As a test, try moving the before print code out of that event and
    populate the datasets before calling Report.Print. Then comment out all
    your other event handlers and see if you are able to print. If so,
    periodically begin adding your code back to isolate the problem.

    --
    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.