You should take a recent back up copy of your file and perform a recover on it to see what the recover operation reports and then open and test your recovered copy (even if it says "no problems found" to see if the recovered file works. If recovering the file fixes the problem or at least identifies a problem, then you'll need to replace the copy on the server with an undamaged copy.
Things to keep in mind about Recover:
- 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.
Thanks very much PhilModJunk.
I thought that would be only option. If the problem ain't obvious the remedies aren't going to be either. Better to kill it and start again. We have plenty of backups thankfully.
Many thanks, Ned.