Random Access Violation on Loading Report from Database
We are loading reports for printing from a MS SQL Server table. We create
the datasources and pipelines programmatically. For the most part it works,
but for a certain report, it often gives us an Access Violation exception
when freeing the report (either through free or by loading another report
from the database). We have tried creating the report object at runtime or
by using a report created at design time and both give the same result. Any
help would be appreciated.
the datasources and pipelines programmatically. For the most part it works,
but for a certain report, it often gives us an Access Violation exception
when freeing the report (either through free or by loading another report
from the database). We have tried creating the report object at runtime or
by using a report created at design time and both give the same result. Any
help would be appreciated.
This discussion has been closed.
Comments
What version of RBuilder do you have. Last week, we also such a problem.
When loading another report after a specific report, we got an AV (in the
source of RBuilder). The guys from RBuilder told me I had to install
version 7, because there seemed to be a problem in version 6.03. Now, after
installing version 7, all problems are gone.
Regards
Wouter Devos
Did you include the source coude of RBuilder 7 in the search path. Maybe
with this information the guys of RBuilder can point you in the right
direction?
Regards,
Wouter Devos
If you are not already doing so, try using the same Owner for the report,
datasources, and datapipelines.
Example...
{assuming Self is the Form}
myDBPipeline := TppDBPipeline.Create(Self);
myDataSource := TDataSource.Create(Self);
myReport := TppReport.Create(Self);
Next try creating the datapipelines statically and get that working before
you dynamically create them. Once you get this working, then try to do it
dynamically. If you still get the error, send a small example to
support@digital-metaphors.com.
--
Nico Cizik
Digital Metaphors
http://www.digital-metaphors.com
purposes. Instead of storing in the database we now store as files and the
problem has gone away.
Thanks for the input.