An insight into FileMaker database corruption and the possible remedies to overcome data loss

FileMaker is a cross-platform relational database management system that has originated from a DOS application. It is an Apple Macintosh application specifically known for its interactive GUI-based interface that enables users to introduce new elements to their existing layouts, screens or forms in the database. It is much similar to the desktop database applications, but exceeds the storage capacity of most of these products. A FileMaker database typically faces corruption due to virus infection, hardware errors, abnormal system shutdown, etc. As a consequence, you lose access to all the valuable data stored in the database. To resolve this problem, you need to go for FileMaker pro database recovery through a trusted third-party tool.

Let's assume a real time scenario. Suppose you are a database administrator. When you try to import your FileMaker database into an excel sheet, you may encounter the below given error on your screen:

"FileMaker Pro Error: Object not found" 

Causes: The above error may occur if you perform the following course of actions:

• On the ‘Data’ menu, you select ‘Get External Data’.
• You click ‘Import form FileMaker Pro’.
• You get all the data to a worksheet.

You can only import records up to a multiple of 500 rows. If you try to import records beyond that multiple of 500, you will receive the above specified error.

Resolution: To resolve this issue, you may try exporting the file as a text file and then using it in MS Excel:

• Start FileMaker Pro and open the database that you wish to import into Excel.
• Go to ‘File’ menu and select ‘Export Records’.
• A dialog box appears. In the ‘Type’ section, click ‘Tab-Separated Text’ or ‘Comma-Separated Text’. Now, specify a new name and click ‘Save’.
• Another dialog box appears. Choose the individual fields you need to export and then click ‘Export’.
• Try to open the saved text file in MS Excel.

If the problem still persists, take help of a competent FileMaker repair tool. These third-party software are proficient in safely repairing corrupt FileMaker databases and retrieving precious tables and other valuable information in the database. Moreover, they support all Mac-Intel based computers with Mac OS X 10.5 and above.

Continue Reading

Possible workaround for FileMaker database corruption

It is difficult to make assumptions of what exactly went wrong when you are dealing with FileMaker database corruption. One might think of 'Compact, Optimize or Recover'. You might overcome a few cases with this technique and get away with the real problem of data loss. Let's find out various options through which you can effectively handle this type of problem.

Frequently, a FileMaker file gets damaged because of unwanted or unnecessary power surges. When ever the application closes unexpectedly, it s very likely that the file will get damaged. FileMaker 9 Server performs a consistency check that typically includes the following set of actions:

• Verifies the block structures (4K blocks)
• Checks if the next and previous blocks are present.

Now, use the following options to recover FileMaker database in the event of corruption:

• Save a Copy As → Clone:

This command is not exactly to fix any corruption. Instead, it enables you to get the clone or an identical image of your file's structure without any data. The significance of this command is that it deletes or removes all the locale info from the file. The locale info includes all region specific data, such as dates, time, etc.

• Save a Copy As → Copy:

This command would allow for creating a block by block copy of your file.

• Save a Copy As → Compacted:

This command implements the 'Compact and Optimize' technique. This process is performed on a copy of the file, thus helping you to protect or safeguard the original data. You can also find the 'Compact' and 'Optimize' options in the 'File Maintenance' menu.

• Recovery command:

This command will ensure that all the invalid blocks are removed from the file when it is recovered. It performs complete scanning of the file and then validates the data blocks. If it finds a corrupt block, it will simply skip the block. A valid block will have the below properties:

• Each block will have a previous and next block containing data.
• The block will have a length of 4K and should be in correct order.
• The block should not be a duplicate of its preceding one.

Continue Reading