1 of 1 people found this helpful
Welcome back, sblake!
Every table needs a unique ID field on every record. These are the Primary keys. Then tables which 'relate' would also have a Foreign key field that would match the PK of it's parent:
Companies::CompanyID_pk = Plants::CompanyID_fk
Plants::PlantID_pk = ???
Certifications may be a table which is joined to Plants, but not directly. Perhaps there should be a table between to link each plant to the different Certifications? That way you can also have an "expires" field that applies to that certification for that plant:
Plants::PlantID_pk = plant_certs::PlantID_fk
plant_certs::CertificationID_fk = Certifications::CertificationID_PK
Think through it a bit and see if you have other rules to define.
When these all link together, you can even see the certifications for all plants in each company, along with all their expires_date!
Thank you for your post!
I'm also going to move this thread from the FileMaker Community Feedback Space (which is specifically for input on the Community itself) to the Discussions Space where you should receive more views and potentially more feedback on this topic!