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

Acces Violation

edited September 2001 in General
Hi

I'm using RB 6.02 and i'm having access violation. I have all my reports
saved on a IB Database. If i edit a report from Report explorer all is fine
but if i try to load and edit a second report, or the same report a second
time in report explorer i get an access violation. This only happens with
report that has a subreports, detail bands, footer bands, etc. If i loda a
report with master/detail bands all runs ok. If i try to print the report, i
get the same errors the second time the report is loaded.

The error ocurrs after the second call to
TppReportTemplate.LoadStart->TppReport.Transfer(aSource:
TppCommunicator)->inherited Transfer(aSource)->Line 2651 in source
if (Owner <> lBand.Owner) then
lBand.ChangeOwner(Owner);

--
Jes?s Angel Garc?a Zarco
Cointec

Comments

  • edited September 2001
    Sorry, for the delay. Can you get this behavior using our interbase end
    user demo? We haven't had any reports of problems like this. After running
    our interbase demo here, I created reports and previewed edited them using
    the BDE and also DBExpress with no av's like you describe. There was a
    cache problem we identified today, in which the report engine is outofsync
    when the next report is loaded. Are you using JITpipelines on a form for
    these reports, or is the data in DADE? If you are using JITPipelines and
    then a subsequent report is loaded, you will need to call
    Report.DataPipeline.Close before the next report is loaded to work around
    this problem until we fix the engine to handle this case.


    Cheers,

    Jim Bennett
    Digital Metaphors


This discussion has been closed.