5 Replies Latest reply on Feb 5, 2014 12:28 PM by montyharper

    Filemaker Pro 12v5 and Mavericks

    montyharper

      Title

      Filemaker Pro 12v5 and Mavericks

      Post

           The Filemaker support website says there is no issue with FMP 12v5 running on Mavericks, however, I just installed Mavericks and now Filemaker keeps "unexpectedly" quitting on me - it never did that before. Anybody else having troubles?

        • 1. Re: Filemaker Pro 12v5 and Mavericks
          davidanders

               It is not universal, and may be due to a third application or utility. But is reported in some of these links.

          https://www.google.com/search?q=filemaker+mavericks

          • 2. Re: Filemaker Pro 12v5 and Mavericks
            philmodjunk

                 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 check for possible problems on a specific computer, you may want to run a utility to check out the hard drive and also to check out the user accounts on that computer for possible problems.

                 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.      
            3.           Recover doesn't always fix all problems correctly
            4.      
            5.           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...
                  

            • 3. Re: Filemaker Pro 12v5 and Mavericks
              montyharper

                   Thank you PhilModJunk,
                    

                   That was helpful for narrowing down the problem. I believe FileMaker is only crashing in a particular file when I try to view a layout that includes a container field. I thought maybe it was Adobe Reader that was the problem (since most of the records contain .pdfs in the container field), but it also crashed when a text file was in the container field. It doesn't crash every time I open that layout, but it doesn't crash on any other layout. Also, it doesn't crash if I remove the container field. I've set up a test database with a container field, and so far it hasn't crashed. 

                   Any further thoughts? Thanks!

              • 4. Re: Filemaker Pro 12v5 and Mavericks
                philmodjunk

                     Is this an interactive container field?

                     If so, you may have an issue with Safari and Adobe's add ins for PDFs.

                     You might try removing them or disabling them and re-enabling them to see if this makes a difference.

                • 5. Re: Filemaker Pro 12v5 and Mavericks
                  montyharper

                       That's kind of what I was thinking, but...

                       I tried putting the same container field by itself on a fresh blank layout. It didn't have any problem. So then I re-built the whole layout from scratch. So far the new layout is working fine with no crashes. I'm hoping that solves it.

                        

                       Thanks for your help!