One-to-One relationship

Discussion created by andrewtraub on Oct 4, 2012
Latest reply on Oct 5, 2012 by Oliver_Reid

What is the best way in filemaker to create and handle a one-to-one relationship?


Say, for example, in OOP I would have a base class called Contact which has 90% of the information that a contact needs, but some contact types need additional fields. So for example, we might have a DateOfBirth field for a Client class which would derive from Contact, but have a SpecialistType for a Doctor class which would also derive from Contact.


To create a fully normalized database, I would normally have a seperate table for Client with the ContactID as the foreign key. Is this best practice for filemaker too? Are there any issues to be aware of when hiding and showing the fields when the Contact type field is changed?