1 Reply Latest reply on Feb 6, 2012 8:29 AM by philmodjunk

    FM Force Quits.



      FM Force Quits.


      Hey Guys,

      I'm a total noob here so I turn to you guys for some help. I have a client that uses filemaker Pro and when this person accesses the DB and tries (according to the client ) to import and/or export files the program force quits on her. I've tried to research the problem and could not come up with the right answer. I have attached a screen shot of what my client has sent me albeit half a screen shot. Any help would be greatly appreciated.


      Thank you.


        • 1. Re: FM Force Quits.

          Any time a file crashes, it's possible that file corruption caused the crash and also possible that the crashes are corrupting the file. Thus, you need to run a few tests both to check for damage causing and caused by any crashes.

          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.

          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 opy 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...