Hi Dan,

I do believe that it *is* a "feature" (no smiley), incorporated to ensure the same behaviour as was found in the original dBASE.
It was called "scope" back then and, though I never understood the reasoning behind it, it was (and still is, I believe) considered correct behaviour.

As had been mentioned, the best protection is to use the IN clause consistently.

Cheers,

Jim N

>>>>* This does not work, no error gets shown, but the replace command
>>>>* does not put anything in the field
>>>>REPLACE prceng.prcpqtyby2t WITH THIS.LIST(THIS.LISTINDEX,1)
>>>>
>>>>* This works
>>>>SELECT prceng
>>>>REPLACE prcpqtyby2t WITH THIS.LIST(THIS.LISTINDEX,1)
>>>>
>>>>Is this a bug, feature, or my misusing a replace on a table that is not selected?
>>>
>>>Add the IN prceng to the end. VFP has a peculiar behavior that if you are sitting at the end of the file in your current area and you attempt to replace in another work area, the replace will fail.
>>>
>>>HTH
>>
>>Is this a feature of a bug that has not been caught yet?
>
>In the hacker's guide, there was an explanation that I don't recall. I believe its a feature. :)