1 Reply Latest reply on Dec 20, 2012 11:29 AM by philmodjunk

    Not responding (crashing) after a new field is created

    AnthonyHanks

      Summary

      Not responding (crashing) after a new field is created

      Product

      FileMaker Pro

      Version

      12 Advanced

      Operating system version

      Win 7

      Description of the issue

      After adding a new field (>Manage >Database) and clickining on OK, FileMaker hangs up and is "not responding". The program then has to be closed. Recover a File fixes the problem, but it continues to recur.

      Steps to reproduce the problem

      >File
      >Manage
      >Database
      Create a field name - eg called x, text
      OK

      Expected result

      Window closes and normal use continues.

      Actual result

      List of fields disappeared but the Manage Database window can still be seen.
      Program is described as "not responding"
      Required to close program.

      Exact text of any error message(s) that appear

      The program is not responding.

        • 1. Re: Not responding (crashing) after a new field is created
          philmodjunk

               Try this in a brand new test file and let us know if you get the same behavior. It could be that recover is failing to fully correct the problem with your file.

               Things to keep in mind about Recover:

               While Recover almost always detects and fully corrects any problems with your file...

                 
          1.           The recovered copy may behave differently even if recover reports "no problems found".
          2.      
          3.           Recover does not detect all problems
          4.      
          5.           Recover doesn't always fix all problems correctly
          6.      
          7.           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.


               And here's a knowledgebase article that you may find useful: What to do when your file is corrupt (KB5421).