Apache OpenOffice (AOO) Bugzilla – Full Text Issue Listing |
Summary: | Report wizard creates broken report when using a query instead of a table | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
Product: | Base | Reporter: | jojasch <kryb> | ||||||||
Component: | code | Assignee: | AOO issues mailing list <issues> | ||||||||
Status: | CONFIRMED --- | QA Contact: | |||||||||
Severity: | Major | ||||||||||
Priority: | P3 | CC: | george.gentili | ||||||||
Version: | 3.4.1 | ||||||||||
Target Milestone: | --- | ||||||||||
Hardware: | All | ||||||||||
OS: | All | ||||||||||
Issue Type: | DEFECT | Latest Confirmation in: | 3.4.1 | ||||||||
Developer Difficulty: | --- | ||||||||||
Attachments: |
|
Description
jojasch
2012-11-05 09:52:07 UTC
Created attachment 79860 [details]
original file. try report Geburtstage
This is the original file. i filled in some data to show the problem of wrong order in the report Geburtstage. The report is created with order options 1. Month (Monat), 2. Day (Tag)... It doesn't sort at all.
there is a workaround for the sorting problem beginning with in the original file: open the query and add the right sorting options, wiev as sql, copy the sql command open the report in edit mode. open the form navigator and select the command and choose properties. paste the sql command into the empty command field and save the report. but this doesn't fix the main bug. Platform: Operating System: Windows 7 Home Premium Version 6.1.7601 Service Pack 1 Build 7601 (x64) Apache Open Office 3.4.1 AOO341m1 Build 9593 Rev 1372282 Confirm the bug I suggest as a workaround to generate a query with the sorted data for the report and then create a view from the query. Reports must have as input the view and so work either statically or dynamically In the example posted by jojash simply generate a view from the query and create a new report with the view instead of query as input. I attach the database testdb changed with the workaround suggested. Created attachment 80303 [details]
database with suggested workaround
see previous comment
Modified Latest confirmation and QA Contact |