Capture.PNG

<div>
Just to add a bit, the reason for that is that in order for the report engine to offer things like groups and performing calculations over a group or the report, it needs to be aware of the ordering in the data, which if done in the query, it would not know.<br />
<br />
So anything specified in terms of ordering in the record source is ignored. The report applies it's own ordering as specified in the report.<br />
<br />
So you should be using a query that does not order any of the fields. &nbsp;If you are, then your doing extra work.<br />
<br />
Jim.
</div>


Just to add a bit, the reason for that is that in order for the report engine to offer things like groups and performing calculations over a group or the report, it needs to be aware of the ordering in the data, which if done in the query, it would not know.

So anything specified in terms of ordering in the record source is ignored. The report applies it's own ordering as specified in the report.

So you should be using a query that does not order any of the fields.  If you are, then your doing extra work.

Jim.

<div>
<div class="content wysiwyg-content">
I am using &nbsp;a query for a recordset for a report and it orders correctly. &nbsp;However, when i run the report it does not. &nbsp;Why?<br />
<br />
What it does seem to order on is the field unique id
</div>
</div>


I am using  a query for a recordset for a report and it orders correctly.  However, when i run the report it does not.  Why?

What it does seem to order on is the field unique id

order by in my report

Microsoft Access is a rapid application development (RAD) relational database tool. Access can be used for both desktop and web-based applications, and uses VBA (Visual Basic for Applications) as its coding language.