There are no such known issues with Replace Field Contents (apple = should be the short cut for Replace Field Contents--not Find and replace.)
But while recover usually fixes a problem with your file. It is not always able to do so. Do you have a back up copy of your file that you can test? You may need to save a clone of the most recent back up copy that does not show this problem and then import all your data from a recovered copy of your working file to get back in business.
Things to keep in mind about Recover:
While Recover almost always detects and fully corrects any problems with your file...
- The recovered copy may behave differently even if recover reports "no problems found".
- Recover does not detect all problems
- Recover doesn't always fix all problems correctly
- Best Practice is to never put a recovered copy back into regular use or development. Instead, replace the damaged file with an undamaged back up copy if this is at all possible. You may have to save a clone of the back up copy and import all data from your recovered copy to get a working copy with the most up to date information possible.
And here's a knowledgebase article that you may find useful: What to do when your file is corrupt (KB5421).