No I dont think it works, you see when you link a query as the master to the
table (detail) then the table automaticcally populates when the master
record changes. A function I'm told QR requires, otherwise the param would
have to be refreshed for every new generated page in the report.

Imagine this, the user selects 10 Master records from my existing TIBOQuery,
each of these has say 10 records of detail in the TIBOTable.

You set the QR detail band to use the TIBOQuery and drop a sub-detail band
on the QR and tell that to use the TIBOTable. Once you have told the
TIBOTable that its master source is the TIBOQuery and its MasterFields is
the connecting field, QR sorts it all out from there. You get a 10 page
printout with independent master information on each page and then a nice
list of 10 detail items on that page.

I have no idea what would trigger an TIBOQuery if I was to use it to change
the param on every new QR page when the master changes.

I do agree though that my select would be easier as I could specify an
order.

This might not sound that important,, but placing an index on that many
records produces about 100mb and I'll have to send all our clients out a new
disk, which I'm trying to avoid doing.

Thanks,

Andy