Hope you have a backup copy that does not exhibit this problem.
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.
Hello Edward Podbelski:
Thank you for posting.
The first step for addressing the failed consistency check would be to attempt repair with the Save a Copy As/Compacted Copy command.
If the compacted copy still fails consistency check choose Save a Copy As/Clone. Check the clone to ensure it passes consistency check. If it passes then export your data from your previous file then import into the newly saved clone.
Please update me if you are still unable to resolve the consistency check failure.