Recovering runtime files (FileMaker Pro Advanced)
Power failures, hardware problems, or other factors can damage a FileMaker database file. If your database solution becomes damaged, your users will need to recover the damaged file. When the runtime application discovers a damaged file, a dialog box appears, telling the user to contact the developer. Even if the dialog box does not appear, files can become corrupted and exhibit erratic behavior.
Once you know which file is damaged, you can recover it using the Recover command, if you have FileMaker Pro or FileMaker Pro Advanced installed. If your user only has the runtime application, however, the Recover command does not appear in the File menu of the runtime application.
To recover a damaged file:
What to expect during the recovery process
During the recovery process, the runtime application:
If users experience unusual behavior in the recovered files, they should revert to a backup copy that was made before the file became corrupt, or contact you for technical assistance.
Documenting recovery for your customers
In your documentation, you should tell your users what to do after a file has been recovered. Tell your users to:
Choose File menu > Save a Copy As.
In the dialog box, choose compacted copy (smaller) from the Save a (Windows) or Type (OS X) list, name the file, and click Save.
Give the compacted file the same filename as the original file.
Related topics 
Checking file consistency
About creating runtime solutions (FileMaker Pro Advanced)
Preparing files for a runtime solution (FileMaker Pro Advanced)
Binding files into a runtime solution (FileMaker Pro Advanced)
Naming runtime solutions (FileMaker Pro Advanced)
Distributing runtime solutions (FileMaker Pro Advanced)
Importing data into upgraded runtime solutions (FileMaker Pro Advanced)
Starting runtime solutions (FileMaker Pro Advanced)