Date: prev next · Thread: first prev next last
2013 Archives by date, by thread · List index

On 01/23/2013 04:22 PM, capemayal wrote:
Build ID: 350m1(Build:2)

I have created a query from one table.  In the query design grid I sort,
ascending, on a 'name' field.

The query works as expected with results sorted on the 'name' field.

When creating a report, using the wizard, with the query as the source, no
matter what I do the query sort does not carry over to the report.

It appears that no matter what field the query is sorted on, the report
always sorts via the ID field, which is also the primary key.

I have tried using the query sort, then using the same field in the report's
sort option;  I've tried using the report control to change SQL Command as
source to the query, and order by 'name' in the report control.

All of this makes no change.  The report does not sort the way the query is

Any help would be appreciated.

View this message in context:
Sent from the Users mailing list archive at
Have you been able to correct your query and report? Where did you get your version of LO 3.5.4? Did it come with a Linux distribution? If so, which one? I ask these questions because I have not been able to duplicate your problem using LO 3.5.7 from the LibreOffice website.


For unsubscribe instructions e-mail to:
Posting guidelines + more:
List archive:
All messages sent to this list will be publicly archived and cannot be deleted


Privacy Policy | Impressum (Legal Info) | Copyright information: 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.