1 Reply Latest reply on Feb 11, 2013 8:42 AM by philmodjunk

    FM Pro 12 " Not Responding" - Looking for advice

    jebber6685

      Title

      FM Pro 12 " Not Responding" - Looking for advice

      Post

           I have been using FM since 1988. I never had any problems with regards to the software until now. 

           I have a PC running Windows 7 Enterprise. I have plenty of RAM and plenty of HD space and I am running FM Pro 12.0 ver 3.

           Recently ( last 2-3 months ) I have been starting FM, the typical FM box that appears often times comes up, remains white, and just remains stagnant. The icon says " FM is Not Responding" and I have to bring up Task Manager to then shut down the program. It will eventually open, but I have to try multiple times and often need to restart the computer. 

           What could be happening? Can anyone give some advice?

            

            

        • 1. Re: FM Pro 12 " Not Responding" - Looking for advice
          philmodjunk

               What does the mouse cursor look like when this happens? You might see a "coffee cup", a "lightning bolt" , "hourglass" or "Esc".

               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”--what you appear to be seeing:

               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:

               msconfig

               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
          2.      
          3.           Recover doesn't always fix all problems correctly
          4.      
          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...