>Hi.
>Using SET RELATION is a good practice with very big databases/tables?
>Thanks!
Let's say you set a relation from TableA to TableB. Just consider that for each and every record you select in TableA, a corresponding record is automatically selected in TableB. Since this is done by an internal use of SEEK, i.e. an indexed search, this should not be exceedingly slow, even on large tables. But the fact of doing the search every time may not actually be necessary, i.e., you may not need the record from the other table every time.
I used to use SET RELATION and SET FILTER for reports; but I now find it very inconvenient. For reports, it is easier to just select all the required data into a single cursor.
Difference in opinions hath cost many millions of lives: for instance, whether flesh be bread, or bread be flesh; whether whistling be a vice or a virtue; whether it be better to kiss a post, or throw it into the fire... (from Gulliver's Travels)