“Neo Code was able to rescue my corrupt file and avoid a total rebuild of the solution, saving hundreds of hours of development time.”
— NC, Dreams Take Flight Calgary

Get Free Estimate
corrupt filemaker

What is FileMaker Corruption

File corruption is not inevitable, but it’s a good idea to ensure that databases are properly backed-up in case of disaster. While FileMaker takes every precaution possible to prevent data loss – there are those rare occasions when your FileMaker Pro file can become corrupted and data loss may occur.

If your Filemaker database exhibits the following signs, chances are, your file could be corrupted:

  • Application is slow.
  • Multiple users report “beachballs.”
  • Application hangs requiring force quitting of FileMaker.
  • Repeatable FileMaker file crashes.
  • Repeatable FileMaker application or server crashes.
  • Records that can’t be deleted.
  • Ghost records (records that can’t be found, but can be seen in a list).
  • Layouts that cause FileMaker to crash.
  • FileMaker Recover command displays message “file should not be used.”
What is FileMaker Corruption

What causes FileMaker Corruption

FileMaker corruption is typically caused by improperly closing a file.  Improper file closure can happen because of human, network or system factors.  For example:
 
  • Catastrophic hardware failure
  • Losing power to your server machine
  • Clients disconnecting without proper termination of their activities
  • Writing / Accessing a bad sector on the hard drive
  • Software or hardware crashes or conflicts
  • Modifying a FileMaker file over a network with poor latency

What to do if you suspect your files are corrupted

If you suspect “some” corruption in your file(s), the best course of action is:

  1. Open your current FileMaker Pro file.
  2. Use the Recover command to test for file damage.
  3. If there is file damage then export the data to a neutral file format (like a Merge file).
  4. Import the data from the neutral file format into a healthy copy of your latest master clone.
  5. On the new file, use the Recover command to test if there is damage.
  6. If there is still damage, go to the next step, or complete the Create Ticket form below for an estimate.
1
2

If you receive an error message about your file being corrupted when you attempt to open it:

  1. Use the Recover command in FileMaker Pro and FileMaker Pro Advanced to attempt to recover your file.
  2. If the recovered version of your file opens, use it to export your data to a neutral file format (like a Merge file.)
  3. Import the data from the neutral file format into a healthy copy of your latest master clone.
  4. On this new file, use the Recover command to test if there is damage.
  5. If there is still damage, go to the next step, or complete the Create Ticket form below for an estimate.

If the file corruption is more severe and you cannot gain access to your current file:

  1. Export your data from your most recent backup to a neutral file format (like a Merge file).
  2. Import the data from the neutral file format into a copy of your latest master clone.
  3. Use the copy of your latest master clone.
  4. Use the Recover command to test if there is damage.
  5. If there is still damage, go to the next step, or complete the Create Ticket form below for an estimate.
3
4

If you do not have a healthy master clone of your file:

  1. FileMaker recommends only using the Recover command to extract data.  Never use a file that has been recovered.  
  2. Complete the Create Ticket form below for an estimate of the cost to completely rebuild your file.  Our tools enable us rebuild a typical FileMaker file in less than a day.

To get a FREE estimate follow these steps:

If you want professional help, send us your corrupt “.fmp12” file and we will send you an estimate to get a new file free from corruption. Note: we do not check for programming faults or wrong field (or other elements) definitions, we only rescue .fmp12 files and our service does not include rescuing FileMaker files that reference external FileMaker data sources.

1

Create Ticket

Create a ticket with the form below. Ticket needs to includes this info:
  • A description of the suspected of the file is included.
  • Login/password or dependent files are only required, to perform specific tests.
  • the names of files you have uploaded using the sync.com link below
  • the [Full Access] passwords
Use this link to upload your files to us: https://ln2.sync.com/dl/022b51530/yp8z43re-s4ep5xcq-rxvjqetu-ic6n4czd
2

Upload Files

All data contained will be kept confidential. We can inspect your files provided they meet the following conditions:

  • The file should not be recovered, cloned, or saved as a copy.
  • If you are able to create a clone of the damaged file(s) that shows the exact same symptoms, you can use this clone instead.
  • Files must be zipped.

Use this link to upload your files to us: https://ln2.sync.com/dl/022b51530/yp8z43re-s4ep5xcq-rxvjqetu-ic6n4czd

3

Review and approve the estimate

After reviewing the file we will reach out to you to schedule a zoom meeting to go over your estimate and options available. If you want to proceed and approve the estimate, we will send you an agreement and an invoice for the non-refundable deposit to get started. Once the non-refundable deposit has been received we will notify you with date we estimate to finish creating a new file free of corruption.

4

Review and approve the estimate

After the new file has been created, we will send an invoice for the time required less balance paid, and a zoom meeting invite. In the zoom meeting we will go over the new file and the post-conversion damage report. Upon receipt of the balance owing, we will send the new file.

Claris Information

The Recover command does not repair files and a recovered file should not be used in a production environment.