1 Reply Latest reply on Feb 14, 2012 12:18 PM by philmodjunk

    programme stops responding and closes

    EileenWaterston

      Summary

      programme stops responding and closes

      Product

      FileMaker Pro

      Version

      11.2

      Operating system version

      Windows 7

      Description of the issue

      Having found the required data, when I then try to create a tab file, the programme stops responding and Windows closes it.

      Steps to reproduce the problem

      Tried several times with the same result.  When I last used this feature, it was fine.

      Clicked on export records: selected tab-separated file: type in name of file and click Save to Documents

      Expected result

      Creation of a TAB file.

      Actual result

      Message: Filemaker Pro has stopped working
      A problem caused the program to stop working correctly.
      Windows will close the program and notify you if a solution is available.

      Exact text of any error message(s) that appear

      Message: Filemaker Pro has stopped working
      A problem caused the program to stop working correctly.
      Windows will close the program and notify you if a solution is available.

        • 1. Re: programme stops responding and closes
          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.

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