Just a stab in the dark but you may need to check the exact name of the recovered file. When recovered it was probably named Intake Recovered.fp5. Make sure that the space after the word Intake has been removed. I have made that error more than once! ;)
As a matter of fact, you are right that there was a space problem in the renaming! (I can't believe something like that would be overlooked- had an OMG moment.) I put the space back that had been lost in translation, but now we get the message that it's looking for the filename without the space, so either way, it's still not finding the recovered file on it's own. I don't know what to try next. I guess I have to find a script that asks for the Intake db to open. And I'm really curious why the error message doesn't have the space. Thanks for your help!
Here's some added info that might help someone tell me how how to fix the problem. Several of the databases contain this script:
Perform Script [Sub-scripts, External: "Intake Record.FP5 (184.108.40.206)"]
(note that there is a space in the name of the database, and I have put that space back into the name of the recovered db.)
The error message I'm getting says:
"IntakeRecord.FP5" could not be found and is required to complete this operation. OK.
Clicking the OK opens the Open File menu, where I click on Intake Record.FP5, and things proceed normally until another related database needs IntakeRecord, and I have to do it again.
The two things I can't figure out, are- where does the IP address get generated, and where does the error message get generated?