1 Reply Latest reply on Sep 21, 2012 9:47 AM by philmodjunk

    FM Pro Advanced crashes



      FM Pro Advanced crashes


           FileMaker Pro Advanced v12.0.2; Mac OS X 10.6.8; MacPro

           FM crashes every time I try to add a new value list and then name it.  I type in the first two letters in the name field in the Edit Value List dialog, FM stops typing, swirling beachball, CRASH.  Every single time.  The only workaround I have found is to copy the text for the name I want to use and then paste it in the name field in the dialog.

           Anyone else seen this?  Any suggestions.


           J D Thomas


        • 1. Re: FM Pro Advanced crashes

               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.

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