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

Problems with Reportbuilder 4.2 for Dephii 4

edited October 2001 in General
When I run on an NT 4 machine everything works great, but when I run on
Windows 98 or 95 I get the following message:

Project TransUL.exe raised exception class EAccessViolation with message
'Access viloation at address 004A11E in module 'TRANSUL.EXE. Read of
address FFFFFFFF'. Process stopped. Use Step or Run to continue.

I only receive this message when I access certain reports. It does not
happen on every report.

I have tried upgrading to TeeChart Pro v5 VCL/CLX. I still get error
messages. It may not be the same message.

Any help you could provide would greatly help?

Thanks
Brian Pembroke
brian.pembroke@anico.com

Comments

  • edited October 2001
    What is the commonality between the problematic reports?- I'm guessing
    you've found that Teechart is one. You may want to consider upgrading to RB
    6.02. Leave your TeeChart 4.x for Delphi 4 installed, and retest these
    reports using the latest version of RB.

    Do you have Delphi on the Win98 machine? Run the app through the debugger on
    the Win98 machine. Point your library path into ..\RBuilder\Source instead
    of ..\RBuilder\Lib and the debugger will provide some more info and a place
    to begin tracing to isolate what is causing the av.

    RB 6.02 does not support the latest version of Teechart for Delphi 4.


    Cheers,

    Jim Bennett
    Digital Metaphors


  • edited October 2001
    Yes, I have Delphi 4.0 installed on Windows 98 machine. I have a report in
    that project that uses Teechart and it works fine. It seems to me the
    common problem is ReportBuilder. I installed ReportBuilder 6.02 for Delphi
    4.0 on the Windows 98 machine and still get the Access Viloation. I also
    have a report that gets this AC that does not use TeeChart.

    Thanks,
    Brian


  • edited October 2001
    When does the report AV? - when opening the report / designing / previewing
    ?

    Take one of the problematic reports, and start removing code and components
    piece by piece until the report begins to work, then work backwards from
    there to create a simple demo and send it to support@digital-metaphors.com


    Cheers,

    Jim Bennett
    Digital Metaphors


This discussion has been closed.