REPLACE scans records specified in the scope (by default NEXT 1) of the
currently selected table, performing the replace in the current record of the target table, unless "IN alias" is included in the command. (If I'm wrong I know I'll be corrected, I determined this when I had a similar problem - the status bar reported 16000+ replacements on a table with 5 records, only 1 record was affected - including the In clause or selecting the target table both cured the problem).

The documentation (V5) states "If the IN clause is omitted, no replacement occurs if the record pointer is at the end of file in the current work area & you specify a filed in another work area"

>has anyone else experience SOMETIMES that when
>
>REPLACE TARGET.FIELD1 WITH SOURCE.FIELD1,;
> TARGET.FIELD3 WITH SOURCE.FIELD2,;
> TARGET.FIELD5 WITH SOURCE.FIELD3,;
> etc....
>
>is issued, the data will not save unless the target table is selected before the replace statement is issued?
>
>If so do you know why?
>
>Thanks a bunch.