After doing a bit more investigation recently, this is a summary of what I've
found (so far) regarding the multiple problems with the legacy Report
Designer-Wizard (RDW) under LO 3.5. For convenience and succinctness, I
thought it might be worth SUMMARIZING the situation in this new message. It
seems there are (at least) 3 different problems/bugs with the RDW under LO
SUMMARY OF PROBLEMS WITH THE REPORT-DESIGNER-WIZARD (UNDER LO 3.5)
1. All reports of course need to be based on an SQL query (whether
pre-existing, or generated 'on-the-fly' by the RDW)
2. When building a Report using the LRD, there are 2 situations (specified
in the first step of the RDW):
a. Select a TABLE from your database
b. Select a (pre-existing) QUERY from your database (referencing the
3. In the first case (2a above), using LO 3.5, the wizard DOES generate the
appropriate query (with the fields and sorting the user has selected), and
stores it in the hidden COMMAND control field. But NOTE, there is still a
PROBLEM in the case where the Report needs to have GROUP HEADERS (i.e.
GROUPED on one of the database fields). In this case, the auto-generated
QUERY is incomplete, and the GROUP BY term is omitted. This can be fixed by
simply editing the QUERY in the COMMAND control field and adding the GROUP
BY term. This is effectively another BUG, in my opinion (the 'Repeated
Headings Bug'). e.g. see here:
4. In the second case (2b above), the wizard either does NOT generate the
query (or does NOT copy it into the COMMAND control field) - leaving it
BLANK. So it has to be entered 'manually'. This is the 'Blank COMMAND field'
bug mentioned elsewhere.
5. When I use the LRD in OpenOffice v.3.3 to generate the SAME report from
the SAME database, the wizard correctly generates the SQL command, as shown
in the hidden COMMAND control field, with the correct GROUPING term, and so
the report runs properly in OO. (It also also runs properly in LO 3.5 once
the hidden 'SORTING' control is added - that's the OTHER 'Sorting control'
bug!). See here...
6. OO also correctly copies the query code into the COMMAND control field in
the SECOND case (2b) above, so there is no 'blank Command field' BUG in OO -
see point 4 above.
7. There seems to be mounting evidence that these problems affect LO 3.5
user on all platforms. See the links above for more info.
I'm not a programmer, and don't have any deep technical understanding of LO
and BASE, but it looks to me that how the RDW works has been changed
somewhere down the line in LO development, leading to these 'bugs' (which,
from what other users have reported, don't seem to affect LO 3.3 - not sure
about LO 3.4).
I hope this summary helps people using the RDW create properly functioning
reports until the problems are sorted down the track. Despite it's flaws, I
find the Report Designer Wizard a very flexible and useful tool, and hope
that it will continue to be supported by the LO development team.
View this message in context:
Sent from the Users mailing list archive at Nabble.com.
For unsubscribe instructions e-mail to: email@example.com
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/users/
All messages sent to this list will be publicly archived and cannot be deleted
- [libreoffice-users] Workarounds for multiple problems with the legacy Report Designer-Wizard under LO 3.5 · frofa
Impressum (Legal Info)
: Unless otherwise specified, all text and images
on this website are licensed under the
Creative Commons Attribution-Share Alike 3.0 License
This does not include the source code of LibreOffice, which is
licensed under the Mozilla Public License (MPLv2
"LibreOffice" and "The Document Foundation" are
registered trademarks of their corresponding registered owners or are
in actual use as trademarks in one or more countries. Their respective
logos and icons are also subject to international copyright laws. Use
thereof is explained in our trademark policy