>>We don't know what these methods are doing. May be they are moving the record pointer or something along the lines. In general I would agree with you, but just to be on the safe side I made the suggestion above.
>
>If so, they will affect the scan the same as the replace. To do what you're getting at, you'd have to push/pop the record pointer before/after the methods are called.
>
>The best practice is to do that in the methods themselves.

Yes, I agree. So, perhaps I was over-protecting :)