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

Problem with setting of Duplex type

edited November 2012 in General
Hi,
I have problem with duplex type:
I have default printer with Duplex set to Vertical.
I open definition in Designer. There was Duplex = dpNone in the definition
before open in designer.
I open Page Setup and I see Duplex = dpVertical. I change it to dpNone and
save.
Now I run print and result is that Duplex is dpVertical again so I have
blank pages.
How I set Duplex to specific value (dpNone)?

Thanks
Roman Krupicka

Comments

  • edited November 2012
    Hi,
    I tested old versions - till version 14.05 was all OK.
    Wrong behavior is from version 14.06...

    Regards
    Roman Krupicka

  • edited November 2012
    Hi Roman,

    Try setting the PrinterSetup.SaveDeviceSettings property to True and see
    if that gives the correct result.

    I also recommend upgrading to RB 14.07 so you have the latest version to
    work with.

    Best Regards,

    Nico Cizik
    Digital Metaphors
    http://www.digital-metaphors.com
  • edited December 2012
    Hi,
    I have RB 14.07. There is different behavior between versions before RB
    14.06 and after RB 14.05...
    Versions < 14.06: Duplex = dpNone works regardless of printer settings
    Versions >= 14.06: Duplex = dpNone works like default duplex in printer
    settings

    Regards
    Roman Krupicka

    "Nico Cizik (Digital Metaphors)" píše v diskusním príspevku
  • edited December 2012
    There is now a patch available that resolves this issue. Registered RB 14.07
    can email support@ and request the patch.


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

    Best regards,

    Nard Moseley
    Digital Metaphors
    www.digital-metaphors.com
  • edited January 2016
    Nard Moseley (Digital Metaphors) schreef op 3-12-2012 om 21:43:

    Hi Nard,

    is there a workaround for this setting of Duplex type problem in version
    RB 14.06?
    What triggers this? Only at 1 customer we experience this.

    Kind regards

    Ruud
  • edited January 2016
    We tackled the problem using dade.

    On the before print event we set duplex to None:
    Report.Printersetup.Duplex:= dpNone;

    Kind Regards

    Ruud



    Ruud Bernards schreef op 12-1-2016 om 13:49:
This discussion has been closed.