1 Reply Latest reply on Mar 25, 2009 11:17 AM by philmodjunk

    Disappearing records in FileMaker 6.04

    MikePR_1

      Title

      Disappearing records in FileMaker 6.04

      Post

      Hello:

       

      I have  a situation and I want to know if anyone had the same problem. In FileMaker 6.04 running in Mac OS and using FileMaker server 5.5v1, i'm serving several files but 3 of them are giving me some pain. I have a Customer Information FIle, related to Customer Cases by a serial number, and a Cases notes related to the Customer Cases by a different serial number. The three files have the "When deleting, delete related records" option checked in the relationship.

       

      The problem is that sometimes in the middle file "Customer Cases", a record can "Disappear" without the Information file or the Notes file loosing a record. I know because I can see in the "Main layout" of the Notes file, orphan records with no information about the case and I can also see a record in the "Information File" without a case in the main portal.

       

      Strange ah?

       

      I checked all the files and rebuild them but still the problem persist every now and then.

       

      Help...

        • 1. Re: Disappearing records in FileMaker 6.04
          philmodjunk
            

          Hi Mike,

           

          I'm currently in the process of converting from 5.5 to 10 so am guessing that my experience 5.5 is pretty similar.

           

          Just to narrow down the possibilities...

           

          How confident are you that the parent record disappeared? If there's is any chance that some action by one of your users can create an unmatched record in one of your child records it would also create what you describe.

           

          Another option: Relationships require healthy indexes in order to function correctly. This is also true for finds and sorts. Sometimes files that have been in use for a while develop corrupted indexes. They will sometimes appear to function correctly until you spot one of the above functions failing to behave as expected.  To rule this possibility out, you can:

           

          Save a clone of your file and then import all records into your clone. Since you are dealing with v6 and multiple tables, do this for all the files concerned.

           

          Perform a recover on the files and then test the recovered files. (Don't put your recovered files into regular use, use them for test purposes only. If you have to recover the file, import the records from the recovered file into a back up clone.)

           

           

          Hope that helps