1 Reply Latest reply on Mar 11, 2013 3:36 PM by philmodjunk

    Crashes when attempting to print, save as PDF, and save as Excel document



      Crashes when attempting to print, save as PDF, and save as Excel document


      FileMaker Pro


      8.5 v 1

      Operating system version

      Mac OSX version 10.8.2

      Description of the issue

      Using Filemaker Pro we have compiled a mailing list of contacts and have printed them in Avery 5160 label format several times in the past. Attempting to print just recently has made the program crash every time. I also cannot save the list as a PDF or Excel document whether in the drop-down menu or using the buttons on the program window. Filemaker crashes each and every time. These seem to be the only functions that cause it to crash, but I haven't explored extensively to see if other functions are crashing it either.

      Steps to reproduce the problem

      Repetitive attempts to print, save as PDF, and save as Excel document.

      Expected result

      Either the list will print, or the list will save as another format that I can print onto labels from another program.

      Actual result

      Filemaker crashes with each attempt.

      Exact text of any error message(s) that appear

      Filemaker Pro quit unexpectedly. Click Reopen to open the application again. Click Report to see more detailed information and send a report to Apple.

        • 1. Re: Crashes when attempting to print, save as PDF, and save as Excel document

               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.

               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? (In your case, try using a new layout for your printing saving as...)
               That may point to a specific layout, script, operation that interacts with your Operating system or other applications...