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

Create new printjob for subreport not working on some systems

edited October 2016 in General
Hello,

We need to create a new print jobs for the output of different
subreports. To do that we set "NewPrintJob" in the category "Generation"
to true and "PrintBehaviour" to "pbSection".

When we print such a report that contains for example 3 subreports we
get 3 different print jobs in the Windows printer queue ... on the most
systems.

However on some systems (not ours, that are systems of a customer) the
windows printer queue shows only one single print job.

The report is exactly the same on each system, so i guess that the
problem is not located in the report itself because with the settings i
described above it should work, i think.

Can you give me a tip what causes the Windows printer queue not to
generate different print jobs?

We currently (still) use RB V 15.04.

Thanks in advance
Ralf

Comments

  • edited October 2016
    Hi Ralf,

    The Subreport.NewPrintJob feature only works when Subreport.PrintBehavior is
    pbSection.

    This feature has been in place for many years - never had any reported
    issues. Internally the feature creates a separate TppPrinterDevice instance
    to print the subreport. This results in a separate print job being created.

    I would check that the report did not get modified in some way.




    Best regards,

    -
    Nard Moseley
    Digital Metaphors
    www.digital-metaphors.com

    Best regards,

    Nard Moseley
    Digital Metaphors
    www.digital-metaphors.com
  • edited October 2016
    Am 20.10.2016 um 17:44 schrieb Nard Moseley (Digital Metaphors):

    After the problems with that report i created a simple test report that was
    designed EXACTLY with that parameters but it still shows the same (wrong) behaviour.

    Could it be an issue with a special printer drive (that prevents creating more
    then one print jon for example)?

    Ciao,
    Ralf
  • edited October 2016
    Hi Ralf,

    I would try the simple test report w/different drivers on same machine. If
    it works with other drivers, then it must be the driver. You could then try
    downloading the latest driver from the manufacturers web site.


    Best regards,

    -
    Nard Moseley
    Digital Metaphors
    www.digital-metaphors.com

    Best regards,

    Nard Moseley
    Digital Metaphors
    www.digital-metaphors.com
This discussion has been closed.