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

Problem with Excel

edited May 2013 in General
Hi guys,
we've got a big problem, if we export our report to "Excel Report File".
Further the report includes two groups and a summary. The export to PDF
works fine, but if we export to Excel, there are empty columns and many
columns are suspended. The memos in header have the same alignment as
the DBFields in Detailband.


We found a workaround, but this could not be a solution.


Do you have any ideas?


You wrote:
David,

XLS is a very primitive format. Rather than exact element positions, a
mapping must be performed from exact page positions to rows and columns.
Therefore there some loss of fidelity. Overall the RB XLS export is
doing an amazing job. As you have found in you align the column header
with the detail and use the same text alignment you get a better result.
You can also get better results by turning AutoSize off on
Labels/DBTexts. You don't mention what version of RB you are using RB
14.07 is the latest release - if you have a prior release you can try
testing with RB 14.07 to see if that provide improved results, I have
improved the XLSReportDevice over time.

For details of XLSReport, check out the RBuilder help topic for
TppXLSReportDevice.


I wrote:
Hi Nico,
I've already use the same text alignment and also AutoSize is off, but
the result is not very good.
If I export only the data the excel export look brilliant.
Can you tell me what is the difference between Excel file Export and
Excel data Export?



You wrote:
David,

I spent some time reviewing the word document with the screen shots you
provided.

1. PersonalNR

Look at the cell just to the left, the one with the caption Mitarbeiter,
there are 3 cells merged together. Cells get merged together to
accommodate the width of the element. In the report layout, try making
the label Mitarbeiter narrower so that it does not cause 3 cells to be
merged together when exported to XLS. If this element is narrower and
takes up only 2 cells then PersonalNR will have a chance to map to the
cell just to the left of where it is mapped now.

2. Column AZ AZG

If the column header and data values are not mapped to the same XLS
column, then I would check the report layout. Make sure the Label and
DBText have the same width and auto-size is off. Make sure the
TextAlignment is the same.




I wrote:
Hi Nard,
Please excuse my late reply, but I was out of office for a longer time.

I invest a lot of time in this report, but it won't work as it should.
The excel export looks not very good. I checked the solution
This discussion has been closed.