How to deal with FileMaker corruption?

FileMaker is undoubtedly one of the best database management tools to create, manage, organize and share important information. Millions of people are using this easy to use database application but just like any other database, FileMaker is also prone to corruption. The most common reasons of corruption are unexpected system shutdown, hard disk issue, FileMaker application malfunction and many more. There are some simple methods by which you can repair your corrupt FileMaker database.

Use Save a Copy As method-> Compacted:
This is easiest and safest method to fix corruption. This command will copy all the data in a new file and rebuild the structure of database. Follow below steps to use this option:
  1. Open your file.
  2. Go to File-> Save a Copy As-> Compacted copy.
Note: This option is available in FileMaker Pro 8.5 and earlier versions.

Make a clone of your file using Save a Copy As -> Clone: This command will create a duplicate copy of your file but without all data. You can import tables, indexes, relations, scripts definitions etc. from damaged file to the new database. This option takes some time in recovering and importing data. Follow below steps to use this option:
  1. Open FileMaker application.
  2. Go to File-> Save A Copy As.
  3. Select a location where you want to save the copy of your file and click Clone.
Note: This option is available in previous versions of FileMaker Pro.

Use Recover option:
This is the most effective command to fix corruption issue. It scans and validates all the blocks in the file and also rebuilds internal IDs of the records. Follow below steps to use this option: 
  1. Open FileMaker application.
  2. Go to File-> Recover.
  3. Select the corrupt file and click Open.
Note: This option is available in FileMaker Pro and FileMaker Pro Advanced.

Comments

Popular posts from this blog

How to Fix Issues with Excel File Save

Ways to prevent corruption in FileMaker database

How to resolve Excel error “MS Office Excel is waiting for another application to complete an OLE action"