3 Replies Latest reply on Sep 15, 2014 7:09 AM by Mike_Mitchell

    Fields to be created in "Estimate Data"


      Hi everyone, im new to filemaker.

      My main job is Pest Control but I have more than 10 years experience in the Information Technology field.


      Ive seen a oportunity in developing small to big systems and Filemaker is a great tool to get the job done according to all the recommendations ive seen and read.


      I have already completed:

      "Filemaker Basics"

      FileMaker Pro 13 Essential Training(Cris Ippolite - Lynda.com)

      Relational Database Design (Cris Ippolite - Lynda.com)

      Relational Database Fundamentals(Adam Wilbert - Lynda.com)


      Currently busy with:

      FileMaker Pro 12 in Depth (Cris Ippolite - Lynda.com)

      Im also attending the Webinars from Filemaker.com


      Next in line:

      Filemaker Training Advanced Course (Filemaker.com)



      Im currently having a question that I could not find clarity in any of the documentation or videos studied.


      In the relation between Estimates and Products, there should be a "Join Table" as the Child/Foreign table.

      Im not sure how you determine what FIELDS must be in that join table....(And why... please give as explenation as mush detail as possible)

      Could anyone please shed some light on this topic please?



      Thank you in advance



        • 1. Re: Fields to be created in "Estimate Data"

          Izan -


          At a minimum, a join table would have the primary keys of the two tables it's connecting as foreign keys. For example, if you're joining Estimates and Products, you might have EstimateID and ProductID.


          Beyond that, you would have additional fields as needed for the particular business flow. For example, you might choose to have a primary key for the join table record itself (e.g., EstimateProductJoinID). Some developers do this to make it easier to script locating a specific record in the join table during scripting; others simply use the combination of the two keys from the parent tables. Mostly a personal choice.


          Other possibilities include anything that is unique to the join table record. Perhaps the join table record connecting an estimate and a product is a line item (because the connection between the estimate and the product represents one line of the estimate)? If so, it might have a unit price. That would go into the join table. Additional possibiities might be quantity, line total (which might be a calculation), discount, description, and so forth.


          Basically, think in terms of what each record in the join table represents (i.e., what entity is it?). That will guide you towards what fields belong there. It's a data modeling question more than a mechanical one. (Go through the exercises in the Data Modeling chapter of the Advanced FTS to get a handle on the concepts.)





          • 2. Re: Fields to be created in "Estimate Data"

            Thank you Mike


            I progressed to the DATA/Relationships in the Advanced Training.

            I'll do my best now


            This is is tough, complete new level of thinking to me.

            • 3. Re: Fields to be created in "Estimate Data"

              Good! New makes the brain grow!