Report Builder and dxGetText
Hi,
I'm trying to use dxGetText to provide internationalisation in a number apps
written in delphi (currently XE2 with RB 15.04). Mostly it's working except
I have an issue with the reports where I am getting an access violation in
the forms that have reports on them. The issue occurs on form-create when
the gxGetText TranslateComponent(self) method (gnugettext.pas) is called.
Has anyone come across this problem?
TIA
WIllie
I'm trying to use dxGetText to provide internationalisation in a number apps
written in delphi (currently XE2 with RB 15.04). Mostly it's working except
I have an issue with the reports where I am getting an access violation in
the forms that have reports on them. The issue occurs on form-create when
the gxGetText TranslateComponent(self) method (gnugettext.pas) is called.
Has anyone come across this problem?
TIA
WIllie
This discussion has been closed.
Comments
In the past, there have been conflicts with certain Dev Express
components and our threaded page generation introduced with RB 14 to
support multiple page viewing in the preview/viewer.
As a test, try setting the Report.PreviewFormSettings.SinglePageOnly
property to True and see if that solves the problem.
(Viewer.SinglePageOnly if you are using the viewer). If you are loading
templates, be sure to set this property after the template is loaded or
in the OnLoadEnd event.
Nico Cizik
Digital Metaphors
http://www.digital-metaphors.com
thank you for the response. There are Dev express components (e.g. cxGrid)
in the project but not on the form of the particular report that is giving
the access violation. I tried those settings but they didn't fix the issue.
Some more information... I have two reports in the project, each on separate
forms and one works OK. They are both fairly basic - the forms comprise a
TppReport, TppDBPipeline, TDataSource and TPPViewer with data provided via a
TClientdataset. The report that errors however does have a
TppSubreport/TppChildReport and 2 Datasource/TppDBPipelines.
Any more ideas please?
thanks
I decided to rebuild the offending unit from scratch, copying over the
components and code snippets from the old unit and the issue has resolved
itself. The only reportbuilder specific differences I could see between the
new and old units was the new version didn't have ppRichTx in it's uses
clause. I added that but this did NOT re-introduce the AV error so go
figure.......
Thanks for your help Nico.