Matt,

I use both, depending on the expected table size of the children.

If the child table is a 'lookup' table which has not a lot of records, I usually use the INDEX and SET RELATION approach.

But, if the child table has a lot (like say, Invoice details), I will go for the PARAMETERIZED approach.

HTH,
Dennis



>In my app, I will have about 10 child CA's that need to be in synch with the "parent" CA, as it is navigated to the next record.
>
>There seems to be two approaches...
>
> 1. Index every CA and use relations to set it all up,
>
> 2. Use parameterized CA's and do a CursorFill() on each one every time the pointer in the parent moves.
>
>
>How do you do it?