>If you are at EOF in the current work area, you're fine. But if you are at the "phantom record", meaning reccount()+1, that's when you will have a problem.

EOF is the "phantom record". EOF is reccount()+1. EOF is not GO BOTTOM.

>
>>I have a program with the following line

>>REPLACE header.terror_inc WITH m.rbTerror + 1

>>
>>My current work area is not actually DWELL and it is at EOF(). I know I need to change the line to

>>REPLACE terrror_inc WITH m.rbTerror +1 IN header

>>
>>For some reason, this code has been making the replacement for several years even when EOF() was true in the current work area. In fact, it is still working in the production version of the system. Are there any situations where the replacement can take place even when it is documented that it shouldn't?
>>
>>I've made a couple of very minor adjustments to the code which I wouldn't have expected to make a difference in this REPLACE statement. The only difference I can think of is that in the current version, I never move out of the current work area. In the test version, I have done a query in a new utility and then moved back into the original work area. Could that have triggered it?
>>
>>I have the #$%$%^ thing fixed, but I still curious why it worked all this time?
>>
>>Thanks to all........Rich