Mike,

It is true that the data in tables is un-ordered.  It is true that in
order to control the order of records in a data set, you need to
explicitly sort the records as required, and yes, this is a job for a
query.  And then, if you use the query as the Record Source of a form,
then the records as displayed on the form will be ordered as required.

However, none of this is really relevant to the method of outputting the
reports that I wrote about.  The report produced should always be
related to the current record on the form, regardless of what the
current record might be.  So the order of the records on the form will
affect the order of the reports, but should not affect the matching of
the data.  So something else in amiss here.

And by the way, you can't do this same approach by directly referencing
a query, as it is not possible to reference the query's "current" record.

Hope that helps.  Please post back with more detailed explanation of the
problem you experienced, with examples, if you need more explicit help.

I should also mention that there are other ways of doing this, by
looping through a Recordset within a VBA procedure... but that's another
topic.