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

Print to File (via TExtraDevices AV)

edited October 2004 in Devices
With Build 7.04 I get an AV if I print to a file (using TExtraDevices) if
the ModalCancelDialog is set at False.

The problem is in ppForms line 1346 (TppCustomCancelDialog.FormHideEvent)

Peter Grimshaw

Comments

  • edited October 2004
    Hi Peter,

    We are unaware of this issue. In my quick testing with RB 7.04 for Delphi
    7, I was able to successfully export to a PDF file with the ShowCancelDialog
    set to False. You may try contacting Waler (support@waler.com) and see if
    they know anything about this issue.

    --
    Regards,

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

    Best Regards,

    Nico Cizik
    Digital Metaphors
    http://www.digital-metaphors.com
  • edited November 2004
    It seems that I am getting the AV when printing as well if the
    ppReport.ModalCancelDialog:=False.

    I have changed it to True to avoid the problem, but I thought you should
    know.


  • edited November 2004
    Hi Peter,

    Which version of Delphi are you using? Does the AV occur for every report?
    If you create a minimal example consisting of a blank report on a form with
    a button, do you still see the AV error?

    --
    Regards,

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

    Best Regards,

    Nico Cizik
    Digital Metaphors
    http://www.digital-metaphors.com
  • edited November 2004
    I am using Delphi 7.

    The problem only seems to occur when the "Accessing Data" dialog is
    displayed (I am using ppJITs for all data access). I will try and build a
    program to demonstrate the problem which I will send via email.



  • edited November 2004
    Hi Peter,

    If you have the ShowCancelDialog property set to False, you should not be
    seeing the "Accessing Data" message. Also if the AV is occuring during this
    time and you are using a JITPipeline to access you data, the issue is
    probably within one of the JITPipeline event handlers. Set your compiler to
    stop on exceptions and point your library path to the RBuilder\Source
    directory to hopefully get an idea where the problem is occuring.

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