Sep 20 2007, 01:39 AM
Access ignores data-source/report's sort order when I put agregate function in A2002 report page footer, eg. Count, Sum, ...
Data source & sort order is created dynamically in a form, ie. users want the same records (filter) & same sort order in reports as they have in a form.
"Groups" in report is not a solution since sort order is dynamic - based on user-defined form's sort-order, ie. sort-order-field-count may differ each time.
Sep 20 2007, 06:30 AM
I wouldn't classify it as a bug. Reports have never respected the sort order of the underlying recordsource: it's always been necessary to using the Sorting and Grouping dialog.
You may be interested in what Allen Browne has at Sorting report records at runtime
Sep 25 2007, 05:04 AM
It must be a bug! It works OK in A97...
Sep 25 2007, 05:09 AM
I think you were just lucky in Access 97. Reports have never respected the sort order of the underlying RecordSource.
It like working directly with the table, as opposed to using a query with the correct ORDER BY clause. Sometimes you'll get the records in the order you want, but you shouldn't rely on it.
Oct 4 2007, 03:14 AM
Then I don't understand why we have OrderBy in Access reports.
IMHO, it really is a bug:
- either the design is poor (reports don't respect data source order ?!?!?)
- or OrderBy doesn't work as designed
It was OK in A97, I mean agreagate functions in footers didn't break data source order.
P.S. I was AFK for several days and I couldn't reply.
This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here