I've use SET KEY but only a SET FILTER substitute. I'm intigued by your suggestion. Would you please provide a code snippet of using SET KEY in place of SET RELATION.
Thanks.

>Actually, instead of a SET RELATION I'd suggest you use SET KEY instead. Much more efficient.
>
>Is it a one-to-many relation? Or one-to-one? Maybe a SQL-slect that builds the dataset would be best.
>
>>Set the relation. In theory the two methods are the same though there is less coding and perhaps fewer operations in the set relation method. Many times an SQL select with a join will work faster then setting a relation.
>>
>>>Situation: Your program loops through table A. For each table A record in the loop, you need info from a corresponding record in table B.
>>>
>>>Is it more efficient to set a relation between the 2 tables before beginning the loop, or (within the loop) to perform a SEEK into the second table? Does the answer differ if table A has 2 records? 10 records? 1000 records?