4 Replies Latest reply on Feb 16, 2012 9:34 AM by DavidJondreau

    Odd Behavior of "Show All Records"

    user10625

      Hello all,

       

      FMP 11, same behavior on Mac and Windows.

       

      Table with around 160,000 records.

       

      Normally, one can use the following to isolate the "current record that the user is sitting on":

       

      Show All Records

      Omit Record

      Show Omitted

       

      And this seems to always work fine.

       

      However, we have noticed that there is one particular record which, when I do "Show all Records", the user is taken back to the first record in the table, instead of staying on the record the user was on. Other records do not behave this way, only this one particular record.

       

      No, the record is not, in fact, the first record. And no, there are no script triggers on the layout or otherwise. And there's no record-level security or anything of that sort.

       

      Finding the record (by it's primary key, or first-last name) works fine. There is no outward hint of corruption (weird ?? marks, etc.) yet, it's starting to feel like it.

       

      Can anyone think of any other things I'm not thinking of to look into? Or has anyone seen this before?

       

       

      Thanks for any responses,

       

      Christopher Bailey

      Baytaflow

      Certified FMP 7

      Certified FMP 10

      Certified FMP 11

        • 1. Re: Odd Behavior of "Show All Records"

          Sounds like a corrupt record. In a copy of the file, are you able to delete this record?

           

          What happends if you duplicate the record and try the same process on that duplicate?

          1 of 1 people found this helpful
          • 2. Re: Odd Behavior of "Show All Records"
            user10625

            >  Sounds like a corrupt record. In a copy of the file, are you able to delete this record?

            >

             

            Yes.  No problems.

             

             

            > What happends if you duplicate the record and try the same process on that duplicate?

            >

             

            Tried this . . the duplicate works fine.

            • 3. Re: Odd Behavior of "Show All Records"
              BowdenData

              user10625 wrote:

               

              Finding the record (by it's primary key, or first-last name) works fine.   There is no outward hint of corruption (weird ?? marks, etc.) yet, it's starting to feel like it.

               

              Christopher Bailey

               

               

               

              Christopher,

              Agree that it sounds like some type of corruption. Couple of thoughts that I would try first. Work on a copy of the dB if at all possible or on the real thing after a full backup.

               

              • Delete the problem record and then recreate it.
                • Does it work now...
              • Turn off indexing on all fields in the table upon which the record is based.
                • Not sure if necessary, but I would tend to close the dB and then re-open it.
                • Go to the table involved and do a search on some of your main fields to trigger re-indexing. Some fields will very likely have already re-indexed due to relationships, etc.
                • Does it work okay now...

               

              HTH.

               

              Doug de Stwolinska

              Bowden Data Services, LLC

              • 4. Re: Odd Behavior of "Show All Records"
                DavidJondreau

                Is the set sorted? Are you sure the user is moving to a different record or is the current record moving?