>>
>>
>>Mike, this has been an interesting thread. Have you used the debugger to determine at exactly which point your record pointer changes in table2. It may be that in opening the new form, or perhaps in loading data from a field, VFP does a select of the table1 work area which causes the related record pointer in table2 to revert back to the first record (I used to see this happen a lot with multiple browse windows open.) There must be a reason!
>>
>>Bob
>
>Yea it has been. Yes I have traced it with debugger. When I use the debugger the problem occurs after the init code has completed. But when I use WAIT WINDOWS to view whats going on then problem occurs right away. I have also determined that this problem only occurs if table1(parent table) has 2 or more records for the customer I am trying to add records for in table2(child table). As of now I have tried all suggestions and even some that are very off the wall but nothing helps.

Have you put a watch on ALIAS()? My suspicion would be that for some reason the parent table is selected at which point it causes the pointer to the child record to revert to the first record again (because of the set relation command). I used to really appreciate the power and ease of set relation, but now I avoid it almost always and will only use it in code during some process (basically NEVER on a form). Your description of what is happening is consistent with the parent table being selected which forces the child pointer back to the first record.

When you solve this problem I will suggest another approach for parent/child records!