>Something from the old days, and I cannot recall how to do that:
>
>I have a parent table selected with a relation to a child table that has an index order set on the foreign key.
>
>I want to scan through the parent table, and during that scan I need to process all records in the child table that relate to the parent table. Surprisingly when I SKIP +1 IN ChildTable it moves to all records, also the unrelated records. I thought it would only skip to those records that are matching the foreign key, and then get to EOF("ChildTable") as if there was a filter active? What am I missing?
Maybe SET SKIP? i.e.
http://fox.wikis.com/wc.dll?Wiki~SetSkipI generally refactor anything using SET RELATION etc. to using SQL. This has the side effect of occasionally cleaning up subtle bugs as well ;)
I bet even amongst VFP maintenance programmers, familiarity with the various SET RELATION etc. ISAM coding techniques is waning.
Regards. Al
"Violence is the last refuge of the incompetent." -- Isaac Asimov
"Never let your sense of morals prevent you from doing what is right." -- Isaac Asimov
Neither a despot, nor a doormat, be
Every app wants to be a database app when it grows up
