>Edward,
>
>I don't agree not to use SET RELATION in favour of SEEK().
>
>SET RELATION when set in the data environment gives you a clear view of the relations between the data and the functions of the form (or screen for FP 2.6)
>
>SEEK may be faster when you deal with only a one or two related tables, but i think ( i've not proven this ) this would not be the case when you have several (say more than 5) tables related to each other.
>
>Besides that. It's a more beautifull option then isue about 6 SEEK()s in a row to update your table after the record pointer of the parent table changes.
>
>"LONG LIVE SET RELATION"

Walter,

If I will tell you what I really think about SET RELATION, I wonder that you take it as personal offense, so I would just stay within well-known fact that SET RELATION just mask on SEEK() behind the scene, so it cannot be faster. In regard to way of updating tables etc., it really depends on the way you or me or someone else develops an application. If it's beatiful to you when pointers move in multiple areas automatically, so it's good for you, but not necessarily for me.