2 Replies Latest reply on Dec 8, 2010 11:31 AM by davidanders

    Large file corrupt file

    BradleyPelletier

      Title

      Large file corrupt file

      Post

      I have a large Filemaker file that was created in FM 8.5. It now will not open. In filemaker 8.5 it just hangs and eventually I have to just force the application to close. I tried a recovery and it hangs at 6 of 16. I then tried to download a trial of Filmaker 11 and open the file and it said it was currupt and tried to open it. It never opened. I then tried to recover the file in FM 11 and it also hangs at 6 of 16. The file is 7.77 gb and contains many pdfs.  Does anyone have any suggestions for getting this file to open.

      Thank You

        • 1. Re: Large file corrupt file
          philmodjunk

          Do you have any back up copies that aren't corrupted?

          Can you open the file and save a clone of it?

          If so check the clone with a recover to see if you can recover it.

          If you can open it at all, you might try deleting major portions of copies of your data base to see if deleting a specific layout or table also deletes the corruption. This is a long shot, but might enable you salvage at least part of your file.

          Can you export your tables to text files? This might enable you to at least salvage the data.

          I also seem to remember that the folks at FMDiff offer a file repair service if you care to pay for it...

          • 2. Re: Large file corrupt file
            davidanders

            How to cope with file corruption

            http://www.fmdiff.com/fm/filecorruption.html

            FileMaker Pro Indexes and Related Problems

            http://fmdiff.com/fm/recordindex.html

            As a database is developed and changed, it is key to save copies and clones for backup.

            If the DB is on Mac, try Windows for recovery, and if on Win, try Mac.

            There is a possiblity that the database is badly fragmented and or the hard drive has hard or soft damage. Try another computer.