Hmmm. I will swear that I got stung once where the REPLACE was ignoring aliases I had on fields to be replaced. Once I included an IN clause the problem was solved. It is interesting that the VFP help says that the fields in the current work area are replaced unless an IN clause is included as I thought.

Oh well - I think I'll just play it safe and always use an IN clause :)
Thanks for pointing that out to me.