There is no guarantee that a recovered file is fully functional. It's possible that the file is still damaged. I'd test a back up copy and if it works, import the most recent data into a clone of this backup--that's best practice anyway.
Thanks for the reply. And yeah, I should have tried this first before I posted, but I was able to reboot the server later tonight (no way they'd let me do that during the day!) and sure enough, it seems somehow FM server was "hung" on just that one DB entry. It works fine now and my recovered file is also in perfect shape. I suppose restarting the FMserver service would also have done the trick.
"...and my recovered file is also in perfect shape"
I gently suggest that you have no way of knowing if a recovered file is in "perfect shape." There is simply no way to know what repairs were made nor if they were made correctly. It's much safer to revert back to a backup copy, importing data into a clone of it if needed.
I've had recovered files where the recover process reported "no problems found" behave differently than the original. (and I don't think it was due to rebuilt indexes.)