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

"Accessing Data..."

edited February 2016 in General
Using RB17.01 enterprise, D7.

I've created a simple report that uses 4 different report templates to
print full colour labels.

Each template has a jpeg image as background, with a single record of
data in a local ClientDataSet (not connected to SQL backend).

So, to print label type A, I clear the CDS, enter the required data,
and load the appropriate template.

I then call ppReport.Print - to screen.

The label shows up with the data from the CDS nice and neat.

When I actually click on "print" within the preview, and the select a
qty to print, about 25% of the time I get the dreaded "Accessing Data"
dialog box - and it sits there for a minute or so.

Oddly enough, if I print multiple times from the same record I will
sometimes get this dialog pop up intermittently. That is, if I need to
print 50 labels, I may do it as five batches of 10 (print qty 10 from
preview 5 times without closing preview). The current "batck of 10"
might print directly, or it might pop up the "accessing data..." dialog
box.

From reading earlier posts about this, it appears this is an issue
where the report can't access the data - but the record is "local" and
filled before printing.

Any suggestions of what I can try to avoid this?

Having used RB for maybe 10 years - this is my first project using
report templates loaded at run time. It's conceivable I'm missing
something fundamental...

TIA

Cheers,
EdB

Comments

  • edited February 2016
    Hi Ed,

    This is not a known issue. Below are a couple tests to try to isolate
    the problem.


    1. If you print directly without going to the preview first, do you
    still get this intermittent behavior?

    2. If you remove the code that loads the template and load it by hand
    before running your app, do you still get the behavior?

    3. If you reduce the number of copies to 1, do you still get this behavior?

    If possible, please create a simple example using a ClientDataset that
    demonstrates this behavior and send it to support@digital-metaphors.com
    so we can research this further.

    Best Regards,

    Nico Cizik
    Digital Metaphors
    http://www.digital-metaphors.com
  • edited February 2016
    Thanks Nico.

    I'll run through the tests, and modify the program to run with standard
    printers (this is for a high-end colour label printer, the page size is
    pretty weird).

    I'll try the modified version on a standard laser printer - if it
    doesn't exhibit the "accessing data..." delays, does this tell us
    anything?

    One other thing - the label printer is 600dpi - to ensure best quality
    I'm using 4875x1275 background images (so there's no interpolation by
    printer on a canvas of 8.125 x 2.125 inches).

    Is there any chance preparing the canvas cause a delay? Is there any
    chance that querying the printer (over USB, and there's a chance one of
    my USB ports is flaky) would cause the "accessing data..." dialog box
    to stay up - that is, some indirect affect on data access?

    Thanks again.

    EdB

This discussion has been closed.