HELP

What to do if you get a 'damaged file' error when opening your FileMaker databases.

How to recover a damaged file.

I have recovered my files but there are now some scripts that do not seem to work properly.

My system crashed and now - although I have re-started all the machines, I can not see the database in the HOSTS dialogue box.

I entered some data into the database, and now it's just not there!

What to do if you get a 'damaged file' error when opening your FileMaker databases:

If your system crashed, or the network had errors - not necessarily a FileMaker error, but something caused your system to freeze, it may result in damage to your FileMaker database if it was open at the time.

When next opening the file you may get an error telling you that your file has corrupted and that you should use the recover command.

DO NOT AVOID THIS STEP!

Immediately go and recover the specified file, using the details below, and ensure that you then delete the original file (otherwise FileMaker will keep giving you this message).

When the damaged file has been recovered, put it to one side and put into your database system a backed-up version of the file that corrupted (one that was backed up prior to corruption, preferably a copy of the original database from a CD if you have not modified the structure since). Then you need to import the data from the recovered file into your backed up version. Then bin the recovered file.

This will ensure that you are working with a stable database, and that you also have all your latest data.

You can then re-open your database and it should run as normal.

USEFUL TIP

You should back up your database(s) every night anyway. If possible instead of recovering a file, simply re-load the previous nights system then you have a non-corrupt version to work with. You will need to however re-key any data that you had entered that day prior to the system crashing.


How to recover a damaged file:

If a file is too damaged to open or use, you can salvage as much information as FileMaker Pro can reconstruct.

To recover a damaged file:

1 Choose File menu > Recover.

2 Select the file to open (the damaged file)

3 In the Save File dialog box, type a new name for the file. By default, FileMaker Pro suggests the previous filename plus "Recovered". Make sure the location you choose for saving the file has enough room.

4 Click Save to save a recovered copy of the database.

FileMaker Pro attempts to recover the file and displays a recovery report.

Copyright (c) 1994 - 2001 FileMaker, Inc. All Rights Reserved.


I have recovered my files but there are now some scripts that do not seem to work properly:

1. Check that you have re-named your file back to its original name.

2. Make sure that you have replaced your original (corrupt) file on the system.

3. If you continued the opening script after you were warned of a damaged file instead of immediately recovering the file, you may have ended up with incorrect files being associated...

4. To correct some of these errors, re-check that your relationships are still correct in the FILE, DEFINE RELATIONSHIPS Menu

5. Go into the affected scripts in Script Maker, and make sure that they are referencing the correct files (especially when using External Scripts).

6. When these are corrected your files should work properly again.

My system crashed and now - although I have re-started all the machines, I can not see the database in the HOSTS dialogue box:

1. Make sure that the Host database is actually open and running on the server (or whoever is normally the host, has the database open).

2. If it is, and you still can not see it, the chances are your network is still down, which is likely to be what caused the crash in the first place. Re-start your network correctly (speak to your support company if you do not know how to do this) then re-start your Host database, you will then be able to see the database in the HOSTS dialogue box as normal.

I entered some data into the database, and now it's just not there!

Make sure you only have ONE SET OF DATABASE FILES for your current system on the network. If you have two or three sets, FileMaker could be opening any files that have the requested file name, and your data could have been entered into an incorrect file.

Keep just one set of databases on the system, and ONE BACKUP off the system on a removable media such as a Zip disk, CD, Tape or RAID system.

In relational files each related piece of information has a 'key' field that relates it to the main database. If the data in the key field (such as a serial number, contact code etc.) is changed AFTER you have put in some related information (such as a letter, or invoice details etc.), it will not be able to find this information again, although it is on the system but no longer 'related' to the original file. Get into the habit of making Key fields that are used for relationships 'un-modifiable' so that this kind of 'loss of data' can not occur.

For any other problems, or if problems persist, visit the FileMaker website at www.filemaker.co.uk or contact FileMaker on one of the technical support numbers listed within your product.

HELP - To learn more about this author, visit Paul Cruse's Website.

Like this article? Share it with your friends

E-Mail | Print | More

Related Articles

---

Related Forum Posts

---

Related Businesses - Evan Elite Authors

The Evan Elite Authors program is currently in beta phase. For details please contact us.