>I just tried that and it works. I don't much like having to create an index on a cursor that is already sorted the way I want. Since I am indexing on the FK field, all those values will be the same, and, IIRC, the indexing will still leave the records in the same order within each FK value. It's been many years since I have used SET RELATION.
>
>>Mark,
>>
>>Wouldn't you have relations from the parent table to the three child tables in stead of the other way around?
>>
>>

>>select parent
>>set relation to key into Child1
>>set relation to key into Child2 ADDITIVE
>>set relation to key into Child3 ADDITIVE
>>

On Childs Define a composite index:

SET EXACT OFF
INDEX ON fnToString(FKey)+DetailOrder1InStringFormat TAG BLABLA1 IN Child1
....
SET RELATION TO fnToString(Key) INTO Child1 IN Parent ADDITIVE
...

If parent have 1 Record only, you can simplified:

INDEX ON ORDER DetailOrder1InStringFormat TAG BLABLA1 IN Child1
SET RELATION TO '' INTO Child1 IN Parent ADDITIVE