>>I have found that set relation between tables is extremely
>>fast. However, it certainly does have it peculiarities.
>>
>>After doing an INSERT INTO, I have found the only way that
>>SET RELATION functions properly is to do a GO RECNO(). Not
>>sure why that is - can someone explain this behavior?
>Tom,
>
>If you are sitting on the parent record and you INSERT INTO the child table. there has been no action taken in the parent work area to cause fox to update the record pointers. GOTO RECNO() is sort of a kick in the pants to fox to say "Hey, something has changed, check it out."

Jim, I am actually adding to the parent record and using the children
records for validating incomming data. I'm surprised at how much
quicker SET RELATION works over SEEK or SQL SELECTs. I kinda
understand why GOTO RECNO() is required after doing an INSERT INTO
into the parent. However, I still must do a GTO RECNO() after doing
a replace on a related child.