3 Replies Latest reply on Aug 11, 2016 8:28 AM by philmodjunk

    FMPro15 crashes on search

    mchancevet@gmail.com

      Hello,

      This is strange.

       

      I have three scripts that search through ~5500 odd records.

      ~ 4 search terms

      Search on some stored TimeStamp field

      also - 3 * unstorred calc field (calculated from related table data)

       

      These three scripts work fine and relatively fast on

      • Mac Air (OSX el capitan)  FMAdv14 8gb Ram
      • ASUS windows 10 crappy processor (bottom of range machine) 2gb Ram = FMAdv14

       

      But !!!

       

      They cause FMPro 15 to crash instantly every single time on

       

           Mac: not sure specs but good machines and also Mac Air bottom of range

           Windows 10 - various machines various specs.

       

      I've tried using defined 'Perform Find' step and by setting fields on a layout in find mode and using an undefined 'Perform Find' step.

      same result for each.

       

      Latest version of FM15Pro as of today (6/8/2016 Aus).

       

      Screen Shot 2016-08-06 at 11.11.29 AM.png

      Thanks,

       

      Morgan

        • 1. Re: FMPro15 crashes on search
          Johan Hedman

          You might have a object on your layout that is corrupt. Try go to another layout that is totally empty that have the same Table occurrence just before you go into Find mode and then after you have searched, go back to your layout.

           

          I would also set a extra If before you go to Order_List layout.

          If ( Get(FoundCount) = 1 )

               Go to Layout Order_Card

          Else if( Get(FoundCount) > 1 )

               Go to Layout Order_list

          Else

               Go to Layout Order_Search/Card

          End If

          • 2. Re: FMPro15 crashes on search
            jerrysalem

            Morgan

             

            Can you try first finding on the stored field, then constraining the found set by the unstorred calcs.

             

             

            Give that a try.

             

            Jerry

            • 3. Re: FMPro15 crashes on search
              philmodjunk

              You may have a damaged file or a screwed up index.

               

              Nearly every time we have a new version of FMP released, I see at least one post where:

               

              "It worked fine on the older version but now it crashes" or some such.

               

              My hypothesis when I read that is that there may be an issue with the file that did not cause a crash with the older version, but does with the new. I have also observed problem files (it was a layout with a corrupted graphic and many versions ago) where it crashed in windows and not in Mac...

               

              So you might recover the file and see what is reported by the recover process. You might also use advanced recover options and just rebuild all indexes. Then test the recovered or reindexed copy to see if the same script causes a crash.

               

              Since this is probably a "live" hosted file in constant use, I'd do this test on a back up copy and see what results I get.

               

              Notes about recover:

               

              1) Recover doesn't catch all potential problems with a file

              2) Recover can't repair every possible form of damage

              3) Recover's repair of a file may not fully correct a problem

               

              So if a file is found to be damaged, best practice, if possible, is to replace it with an undamaged back up copy. This may require saving a clone of the back up copy and importing all data from a recovered copy of your most recent copy of the file in order to produce an undamaged copy with up to date data.

               

              4) But if you use advanced recover to only re-index the file (copy file blocks as Is), then this file should be identical to the original except for the new indexes and thus can be safe to use assuming that a messed up index was the only problem.