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

Access Violations at design time

edited June 2003 in General
I am getting a ton of access violations and "invalid pointer operations" at
design time when switching between preview and back. I am using D7 and RB
Enterprise.

Any suggestions?

--
Reid Roman
Future Generation Software
http://www.fgsoft.com

Comments

  • edited June 2003
    Reid,

    Are you using ReportBuilder 7.02 Build 2? If not, please download the
    latest version. Make sure your report object is located on a Delphi form
    and not a datamodule or webmodule. Can you see these AV's when running our
    demo projects? If so, please provide the exact steps you took to create
    these errors so we can try to re-create the issue here.

    --
    Best Regards,

    Nico Cizik
    Digital Metaphors
    http://www.digital-metaphors.com
  • edited June 2003
    "Nico Cizik (Digital Metaphors)" wrote in
  • edited June 2003
    Hi Reid,

    Check that the .dcu files located in the \RBuilder\Lib\... directory are
    dated 03/03/17 7:02am to be sure you have the latest version of
    ReportBuilder. Are you able to reproduce the AV errors that you were
    receiving with our demos? You should be able to use a DBCalc instead of
    trying to count the GroupHeaderBands.

    The reason the code scrolls behind the scenes when loading a report is that
    when RAP is being used at Delphi design time, your report is created behind
    the scenes on the form to save the layout before the report begins
    generating to the design-time previewer. The reason is RAP code during
    report execution can change the layout. When you return to the design
    workspace, the cached template is re-loaded restoring your template to its
    origonal settings ensuring that your RAP code did not change your layout so
    the next time you run your report, it will run correctly.

    --
    Best Regards,

    Nico Cizik
    Digital Metaphors
    http://www.digital-metaphors.com
  • edited June 2003

This discussion has been closed.