1 Reply Latest reply on Aug 20, 2012 1:51 PM by philmodjunk

    Checking for consistency issue when opening files.

    WendyAtkinson

      Summary

      Checking for consistency issue when opening files.

      Product

      FileMaker Pro

      Version

      filemaker pro 11.2

      Operating system version

      windows 7

      Description of the issue

      When we close our filemaker program and reopen the files we get a message "This file has been improperly closed, checking for consistency." This will take in some files an hour to reopen. Our filemaker file is 4.8g so we are dealing with a rather large file. Why does this continue to happen even when we exit the files properly? How do we resolve this issue?

      Steps to reproduce the problem

      close file and reopen

      Expected result

      do not expect the error message

      Actual result

      we continue to get the message "This file has been improperly closed, checking for consistency."

      Exact text of any error message(s) that appear

      This file has been improperly closed, checking for consistency

      Workaround

      none

        • 1. Re: Checking for consistency issue when opening files.
          philmodjunk

          The file could be damaged.

          The file could have been improperly closed--such as would happen with a crash or a force quit.

          The file could have been copied by the OS or a backup utility while open. (The copy, not the original will then require a consistency check...)

          When a file is correctly closed, a flag on the file is set to show that it was properly closed. When the file is re-opened, FileMaker checks to see if this flag was set. If not, it runs a consistency check.

          If you are closing the file with close file, quit aplication or by clicking the close button and the file has not been improperly closed or copied, you shouldn't get a consistency check. If this is the case, you need to run a recover on your file and test the recovered copy to see if the copy undergoes an automatic consistency check when opened.

          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.