1 Reply Latest reply on Mar 21, 2012 10:00 AM by philmodjunk

    FileMaker Pro 11.0v4 crashing on Mac OS Lion



      FileMaker Pro 11.0v4 crashing on Mac OS Lion


      FileMaker Pro



      Operating system version

      OS Lion 10.7.3

      Description of the issue

      Just installed FileMaker Pro 11.0v4 on iMac, OS Lion. Opened a file from my previous version (FileMaker Pro 8), saved a clone copy, edited database by deleting old fields and adding new fields. Now, when entering data, the file will close without warning. Have performed a restart, same problem happens. Please advise.

        • 1. Re: FileMaker Pro 11.0v4 crashing on Mac OS Lion

          Sometimes an older version will "tolerate" a problem with a file. Then you upgrade to a new version, it doesn't tolerate the problem and you get crashes that you didn't have before. That's one possible explanation--it's not the only possibility.

          Figuring out why FileMaker is crashing can require some sleuthing to rule out possible issues.

          Basic diagnostic tests to perform when you get frequent crashes or “Hangs”:

          Does the crash only occur with a specific file?
          Test by creating a small sample file and see if opening it and working with it also generates a crash. If it crashes too, the problem likely lies with the computer or it's installation of FileMaker. If it does not crash, it becomes more likely that there is a problem with the file.

          To rule out some other issues with your specific computer on Windows systems,

          Select Run from the start menu and type in:


          Then, under the Services tab, you can stop all non-Microsoft services. If this solves the issue, then you need to look at what services you stopped and see which is one is the culprit.

          What is reported when you recover the file?
          The file could be damaged. Not only can file damage cause crashes, but the crashes (or forced quits after a "hang") can damage your file. You may need to test a recovered copy to see if it works without crashing.

          Things to keep in mind about Recover:

          1. Recover does not detect all problems
          2. Recover doesn't always fix all problems correctly
          3. 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.

          Does it always crash when you are doing the same thing with your file?
          That may point to a specific layout, script, operation that interacts with your Operating system or other applications...