Accessviolation problem on applikation exit
After upgrading an app from D6/RB6 to D7/RB7.03 we get EAccessViolation on
application exit.
An exception is also rasied if the report is excuted twice (viewed or
printed)
The RB components are placed in a Datamodule.
If i remove the RB components the no exception is rasied on exit.
The D6 app worked fine without exceptions
What's the problem with the RB7 pro?
Mikael Norrman
Atona Consulting Partners
mikael.norrman@atona.se
application exit.
An exception is also rasied if the report is excuted twice (viewed or
printed)
The RB components are placed in a Datamodule.
If i remove the RB components the no exception is rasied on exit.
The D6 app worked fine without exceptions
What's the problem with the RB7 pro?
Mikael Norrman
Atona Consulting Partners
mikael.norrman@atona.se
This discussion has been closed.
Comments
If you create a new report and execute it, do you still receive the
exception? Are you able to trace into the ReportBuilder code or your code
where the exception is occuring? We have had no issues like this with
people upgrading from RB6 to RB7. If possible, please create a simple
example that causes this error and send it in .zip format to
support@digital-metaphors.com.
--
Nico Cizik
Digital Metaphors
http://www.digital-metaphors.com