Empty pdf files
Hi everyone!
I have same problem with export to pdf.
I have an empty pdf files.
I work with Delphi 2010 and also
use ReportBuilder 12.05 Enterprise build 251.
I read, somewhere, that for computers with windows7 it seems to be
related to
operating system's "Regional and Language options" settings.
Is it true?
If is true, there is a patch or new release to fix this problem?
I have an important client waiting for a response to this problem.
Best Regards
I have same problem with export to pdf.
I have an empty pdf files.
I work with Delphi 2010 and also
use ReportBuilder 12.05 Enterprise build 251.
I read, somewhere, that for computers with windows7 it seems to be
related to
operating system's "Regional and Language options" settings.
Is it true?
If is true, there is a patch or new release to fix this problem?
I have an important client waiting for a response to this problem.
Best Regards
This discussion has been closed.
Comments
Starting with RB 12, if your application (at any time) alters the
built-in Delphi FormatSettings, the ReportBuilder ppFormatSettings also
need to be updated. The issues with PDF are generally caused by
altering the FormatSettings.DecimalSeparator in code.
You will want to add the following line in order to resolve the issue.
FormatSettings.DecimalSeparator := ',';
ppFormatSettings := FormatSettings; //Add this line
Nico Cizik
Digital Metaphors
http://www.digital-metaphors.com
Hi Nico,
thanks for the reply, but this problem was solved with the 14.x without
adding the line of code that I have indicated ?
Best regards
Mauro Catellani
This is a requirement for all versions of ReportBuilder from RB 12 on.
Nico Cizik
Digital Metaphors
http://www.digital-metaphors.com
Hello Nico
Forgive me for jumping in, but this is disastrous for us! We have to
support multiple currencies in our app and we do this NOT by messing
around with global formatting settings, but instead loading these
settings from a table into a class that dynamically handles display
formats in output like the DevExpress Grid or Report Builder reports. I
have RAP pass-through procedures that can assign the Displayformat to
any currency fields according to the currency type that applies to them
and it works a treat. I also have a custom TppDisplayFormat class
registered to handle more manual ways of specifying currency formats.
This bit of news about PDF output is very bad indeed and tests show that
PDF output is now broken if the currency being displayed doesn't match
the global Delphi settings. Surely this is NOT the way to do it as it
precludes the possibility of displaying more than one currency in a PDF
output? Why can't the PDF engine just respect the DisplayFormat settings
that have been assigned to each component on the report?
I've put a lot of work into our model of currency formatting - please
come back with something reassuring?
TIA, Paul
I'm a bit unclear about what exactly you are changing. If possible,
please send a simple example showing this behavior to
support@digital-metaphors.com in .zip format and I'll look at it for you.
The only requirement here is to keep the global FormatSettings in sync
with the ReportBuilder ppFormatSettings (specifically the decimal
separator). All (numeric) text exported to the PDF device is sent
through the TppPDFCanvas.ExtToStr routine. This automatically replaces
the decimal separator (defined by ppFormatSettings.DecimalSeparator)
with a period ".". If you change the global FormatSettings without also
changing the ppFormatSettings you can see how this would cause issues.
Nico Cizik
Digital Metaphors
http://www.digital-metaphors.com
issue. This thread addresses the "Empty PDF" issue when altering the
FormatSettings global property. If you are able to see objects inside
your exported PDF, this is a different problem.
Please send a simple example to me and I'll research it for you.
Nico Cizik
Digital Metaphors
http://www.digital-metaphors.com
over this and done some rather crude tests. I've been busy covering
support myself today (!!!) so not had time to check this out properly.
For the time being I please ignore this - I may have been making a fuss
over nothing, in which case I apologize. I'll come back to you if I need to.
Paul