1 Reply Latest reply on Feb 18, 2013 11:23 AM by philmodjunk

    FileMaker Pro 12 - container field crashes



      FileMaker Pro 12 - container field crashes


           We recently upgraded to 12.  We've been using FileMaker Pro for quite sometime, however i am new to it and am going through the FileMaker Training Series.  I'm to the point in the training of container fields, and whenever i get to the part where i need to create a container field and insert anything other than a picture file (pdf or mov or doc or xls) it starts off as if it's ok, but when i click on it (left or right click), the whole program crashes.  This isn't just within the training series, but is carrying into our live work system as well.  Since the upgrade, there have been issues with the container fields.  Can someone help me fix it?  Or is a FM bug that needs to be fixed?  The error is not specific, it just states that FileMaker has encountered a problem and asks if an error report should be sent or not.

           Jenn Davis



        • 1. Re: FileMaker Pro 12 - container field crashes

               What method and options are you using to insert into the container field? What data format optimization option was specified?

               You may want to use the following to narrow down the list of possible causes:

               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.

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