>>You can perform a REPLACE on a table that isn't the currently selected table without using the IN clause, if you prefix the columns with the appropriate alias:
>
>While you can do that, it's not a good idea and it runs the risk of not behaving as you expect. You're at risk if the current work area is at end of file, and you may not see what you think you will if any of the work areas are at EOF.

That's what I illustrated with my code samples.

>In my view, no REPLACE should address more than one table,

For the sake of simplicity, readability and maintainability, agreed. Break the rule only if you understand the potential consequences, and test thoroughly ;)

>and every REPLACE should include the IN clause.

... as I said in my first message in this thread.

>For that matter, every Xbase command that accepts it should include the IN clause.

Agreed.