Unfortunately the order is the important part. The tables do not have
the same number of records, though I hope there was a way to end the
select when one of the three ran out of records. I'm am unclear about
what you mean when you say the 'table have no order' do you mean index?
A Table is - logically speaking - an unordered "heap" of records. This
isn't an Access limitation; it's a fundamental principle of relational
database design. You can use an Index to make querying the table with
an Order By clause faster and more efficient; and as a practical
matter the table will be *presented* to view in Primary Key order -
but you have absolutely no control over the order in which records are
stored on disk; if you create a query joining the three tables,
without an Order By clause, then you'll get the records in whatever
order the query optimizer finds most convenient. It might be in the
order you see them in the table datasheet, but it probably won't!
What is the actual structure of these tables? What is the Primary Key
of each table? What field (WITHIN THE TABLE) defines the desired
sequential order? Or, if the data comes from outside Access, whence?
Is there any defined order in this source?
I think what you'll need is some VBA code opening three recordsets to
read the three tables, and a fourth to write data out - but even these
will need *something* to control the order. A Table recordset will
(probably) be returned in Primary Key order but if you have no Primary
Key you may be out of luck!
John W. Vinson[MVP]