Recover Script

[transpower]

I'd like to have a user click one button and automatically recover the file. I realize that the script must be run from an external file, because the file to be recovered must not be open. I can select the damaged file of course but the problem is with the name of the recovered file: FileMaker will not allow the same name as the damaged file. So I have a script which creates a recovered file which is not the same as the original. Of course, I can instruct the user to check the byte sizes of both the original and the recovered files; if they're the same, do nothing; if they're not, copy the recovered file to the original file name. But I'd rather have FileMaker do all of this. Any suggestions?

[RalphL]

I wouild never have a customer use the Recover command. They need to go to last backup. Recover is used to recover data. It may or may not recover more but you are playing with fire if you use the recovered file for anything other than getting data.

[transpower]

But this is for a stand-alone Developer package. According to the Core Solutions Filemaker Development Standards, a Recover button is recommended. I suppose I can pause the script and instruct the user to Start | Run | cmd | cd directory and compare the files and copy over if necessary.

[RalphL]

It is interesting that they call for a recover button in run-times but no where else. I wonder what they mean by recover.

[RalphL]

When all else fails, look in the manual. Page 32 of FileMaker Delveloper 7 Devloper's Guide. "Recover command does not appear in the File menu of the runtime application."

The manual goes on to say to import the data from the recovered file to a copy of the original database. This would mean a clean copy, no crashes.

[transpower]

OK, I see that on p. 32 of the Guide. I knew that the Recovery option was not listed in the File menu, but I thought that one could use the Recover step in a script! (The compiler doesn't give any warning that Recover cannot be used.) So, I think I'll just use the button to inform the user what to do, as per p. 32. Thanks.