EAccessViolation

rbuser

I have a fairly complex RB report... it is generated from a combination of
Flash Filer data tables and KbmMemTable memory tables - it contains several
sub-reports, etc. I've started getting an intermittent EAccessViolation
error. It's totally unpredictable. One time I can run the report and the
program will generate 200 + pages with no error. I can then run the program
again (against the same data) and only generate 5 or 6 pages before I
receive the error. The next time it may or may not run to completion. It
never errors out at the same place in the report. Any idea where I might
start to look for the problem. It just seems so random - Any suggestions
are greatly appreciated.

Joe Hutchins

nicocizik

Hi Joe,

Which version of ReportBuilder/Delphi are you using? At what time during
your application are the errors occuring (i.e. during report generation,
printing to the printer, using the end-user designer, etc...)? You might
try simplifying your report a bit by commenting out your event handler code
and see if the AV still occurs. Then periodically add the code back to
isolate the issue.

--

rbuser

ReportBuilder Professional - Version 6.02
Delphi 5.0 with Update Pack 1

I get the error as the pages are being generated. It comes up for preview -
after viewing the first page, I send the report to the printer. As I
mentioned, sometimes it prints OK... but many times it will fail with the
EAccessViolation error - and the error occurrs at different places in the
report. If it would fail the same way everytime, maybe I could find my
error... but it never fails in the same place twice. I've been trying to
isolate my error... but so far now luck.

Joe Hutchins

nicocizik

Hi Joe,

Unfortunately this is not a known issue with ReportBuilder. My suggestion
would be to back up any report tempaltes you are using and download a trial
version of ReportBuilder 7.03 to test with. If this does not help, you will
probably need to start simplifying your report by removing all third party
components and event code from your app and seeing if you can still generate
the error.

--