2 Replies Latest reply on Jul 5, 2013 10:50 AM by BruceHerbach

    Primary ID Help

    kaostika

      I have a client that uses excel and is converting to Filemaker.

       

      They will have in Excel something like this

       

       

      201412041

      201412042

      201412043

      201412044

      201412045

      201412046

      201412047

      201412048

      201412049

      201412050

      The Next week is as follows.

      201413041

      201413042

      201413043

      201413044

      201413045

      201413046

      201413047

      201413048

      201413049

      201413050

      Each Person has their own set of numbers. They want to recreate this system in Filemaker. The issue is that I need to keep track of all these numbers in advance and assign them when my filemaker record are made. They assign their jobs maually in excel and sometimes they skip numbers if a job goes into another week. If they go outside their numbering system they contact accounting to get a new number. I am attempting to explain the problem with this system. I can recreate it, but I feel that it will fail. Has anyone else had a similar experiance

       

      Oreste

        • 1. Re: Primary ID Help
          mikebeargie

          Hi Oreste,

           

          I would calculate the reference field as just that, a reference field, for their display usage satisfaction. I would NOT setup any relationships going forward based on this unless you can guarantee that your generated calculation always evaluates to a unique number.

           

          On the backend out of the user's view, I would use a standard primary auto-enter serial number or UUID as a unique serial to use in all of my relationships.

          • 2. Re: Primary ID Help
            BruceHerbach

            Hi,

             

            I would advise using Mike's suggestion.   Use a a standard Primary key for all records connected by a foreign key.  Provide a displayed/editable field for the key value provided by accounting.  You could add a script trigger/script that updates all related records with a new version of the accounting key if they change it because of delay into the following week.  Do not use the accounting key value in a relationship.