>Carl and Larry,
>
>I don't think this is a "bug", but rather I *believe* that it is the "standard" Xbase way of dealing with "scope".
>In ordinary folks terms. . . 'if the current work area is at eof(), then any other work area is also assumed to be at eof()'.
>

If it walks like a duck...

>I think it was VFP 3 which introduced the "IN" clause to many of the commands, essentially allowing us to address each relevant work area specifically, thus overcoming the assumption which is inherent otherwise.
>
>Cheers,
>Jim N
>
>>>I believe that you are running into a known bug. The bug is if the
>>>currently selected area is eof() then a "REPLACE otherarea.field..."
>>>doesn't work
>>>
>>I'm with you on this, too. I know I've run across it before.
>>
>>And, I don't know whether or not this applies here, but sometimes
>>an implicit scope for NEXT 1 doesn't work as expected. I've found
>>in the past that sometimes a REPLACE WITH will
>>not do a thing (including no error message), but if I add the
>>explicit scope clause in, "NEXT 1", to get a REPL NEXT 1
>>WITH , it works and life is good again.
>>
>>==Carl