1 Reply Latest reply on Feb 4, 2013 9:11 AM by philmodjunk

    Value updates in relationship tables

    DanMatley

      Title

      Value updates in relationship tables

      Post

           I have a Filemaker set up for managing job applicants. Applicants go in one table, and there's also a seperate table for Job Positions - the two are connected by a corresponding PostionID field in both tables. For instance:

             
      •           Table : Applicants           
                         
        •                     Field : Name
        •                
        •                     Field : Years of Experience
        •                
        •                     Field: PositionID
        •           
             
      •      
      •           Table : Job Positions           
                         
        •                     Field : PositionID
        •                
        •                     Field : Position
        •           
             

           In the Form View I have displayed the role each applicant is applying for by adding the field "Positions::position". HOWEVER, if I were to change this value to something else - ideally this would update the PositionID in the Applicants table for that applicant, but instead it changes the value associated with the PositionID in the Jobs Positions table.

           How can I correct this?

        • 1. Re: Value updates in relationship tables
          philmodjunk
               

                    HOWEVER, if I were to change this value to something else - ideally this would update the PositionID in the Applicants table for that applicant, but instead it changes the value associated with the PositionID in the Jobs Positions table.

               That should not happen. You should check the design of your layout to make sure that you are modifying Applicants::PositionID and not Job Positions::Position ID when you edit the value in this field.

               You might also consider the fact that applicants may apply for multiple positions either at the same time as time passes and new positions become available. That gives you the need to link one applicant to many positions as well as one position to many applicants--a many to many relationship that will be best managed by inserting a join table in between Applicants and Job Positions.

               Not only can such a table manage the many to many linkage, data specific to one applicant's efforts to get one specific job can be documented in fields defined in that join table. That allows you to record which applicants, for example, get selected to interview for a specific position if you had fields for that purpose to the join table.

               Applicants----<applicant_position>-------Job Positions

               Applicants::__pkApplicantID = applicant_position::_fkApplicantID
               Job Positions::__pkPositionID = applicant_position::_fkPositionID