2 Replies Latest reply on May 10, 2012 11:54 AM by philmodjunk

    FM 11 advance to FM 12 Data corruption

    nramirez1978

      Summary

      FM 11 advance to FM 12 Data corruption

      Product

      FileMaker Pro

      Version

      Filemaker pro advance 12

      Operating system version

      windows 7 pro  64bit

      Description of the issue

      HI,  I had a few databases under FM 11 advance that i migrated into FM 12 advance last week.  I been updating my databases just fine and all the sudden i'm getting a data corruption error.  error says  "name of file.fmp12" was not created wiht Filemaker or is severely damaged and cannot be opened.

      I try to recover my databae and it recovers fine, but when i try to open it it fails and i get the same error above..

      out of 20 databases i have 3 that have this issue.

      the largest database is about 200mb.

      Steps to reproduce the problem

      go to folder and double click on the database and that's when the error comes up.

      Exact text of any error message(s) that appear

      "name of file.fmp12" was not created wiht Filemaker or is severely damaged and cannot be opened.

      Workaround

      nothing yet..

        • 1. Re: FM 11 advance to FM 12 Data corruption
          TSGal

          Soccer1978:

          Thank you for your post.

          It's difficult to determine what is the problem with those three files without seeing them.  Therefore, I would like to see your FileMaker Pro 11 files to determine if the corruption occurred before or after migration to FileMaker Pro 12.  I know the files are large, so check your Inbox at the top of this page for instructions where to send the files.

          TSGal
          FileMaker, Inc.

          • 2. Re: FM 11 advance to FM 12 Data corruption
            philmodjunk

            Tests you can do:

            Do a recover on the Filemaker 11 files with FIlemaker 11. Perhaps there was an issue in the file before they were converted.

            Convert one of these files again and do a recover on the file with Filemaker 12.

            Things to keep in mind about Recover:

            While Recover almost always detects and fully corrects any problems with your file...

            1. The recovered copy may behave differently even if recover reports "no problems found".
            2. Recover does not detect all problems
            3. Recover doesn't always fix all problems correctly
            4. Best Practice is to never put a recovered copy back into regular use or development. Instead, replace the damaged file with an undamaged back up copy if this is at all possible. You may have to save a clone of the back up copy and import all data from your recovered copy to get a working copy with the most up to date information possible.