1 Reply Latest reply on Jun 26, 2014 10:53 AM by philmodjunk

    Help/Guidance Please?!

    giametti

      Title

      Help/Guidance Please?!

      Post

           My large database has been acting up for a while.

            

           Symptoms:

           Frequent crashes (Filemaker has quit unexpectedly). Sometimes as many as 5-6 times a day. Sometimes not for a while. Occurring a lot since I upgraded to FMA 13 in January.

           Recent file not closed errors. ("Filename" is currently in use and cannot be opened...) or ( The primary file, "Filename" is either not part of this application, is damaged, or is already open.) These errors have only been happening for the past several days.

            

           Background:

           I'm a professional furnituremaker who has used Filemaker to run my business since Filemaker 3. It's grown A LOT since then in function and scope. It keeps my customer files, does accurate estimates of time and labor, handles inventory of product and materials, keeps a track of sales and expenses, and even functions as a small POS when I sell at craft markets. All my Filemaker knowledge is self-taught or from lurking in FM forums.

           I've had an eye on making the solution available to other craft artists as a runtime solution for a few years--working in spare time to make it functional for craftspeople other than woodworkers. I currently have a couple of other craftspeople functioning as testers and advisors. I've been making runtime solutions for them both in Mac (my platform) and Windows 7, running in emulation through Parallels.

            

           I believe the File Not Closed errors may stem from trying to edit the file while in Windows this past weekend, though it may have come earlier. (I wasn't aware that accessing the file through Parallels/Mac file sharing was a no no. I've since turned all file sharing off.)

            

           What are my options? Rebuilding the database from the ground up would be a monumental task. The oldest copy I have is from 2010, but I'm unable to open it (I strengthened the user password since then and don't remember the old one). How do I guard against future corruption (if that is what it is)? How do other people using the runtime also guard against corruption?

            

           I believe the solution has value on the market, but in it's present state it's too unstable to market.

            

           Jim Eddy

        • 1. Re: Help/Guidance Please?!
          philmodjunk

               Crashes can damage a FileMaker file.

               A damaged file can crash

               What you describe appears to be a file that is damaged either as a result of a crash or from other causes and now crashes because it is damaged.

               Thus, you should run a recover on this file to check it for damage. Hope you have backup copies.

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