Jump to content
View in the app

A better way to browse. Learn more.

FMForums.com

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

One-to-one relationships

Featured Replies

Hello,

I have searched the file maker 8 user guide and many websites but can't find any thing about one-to-one relationships in filemaker. Does anyone have an idea about how I can set this kind of relationships.

Thanks in advance ;)

One to one relationships aren't very useful. An example:

We have a bunch of information about "People". We also have "unique ID numbers" of which each person can only have one, and each ID number can only be associated with one person: a typical one-to-one relationship.

One-to-one information could be kept in a separate table, but because it's never duplicated, and there must always exactly the same amount of ID numbers as there are people, it's easier and more correct to store the IDs in a field in the same table. Hence, information that exists in a one-to-one relationahip is about the same entity and needs to be in the same table.

Should you be asking about one-to-many or many-to-many rekationahips? These are useful and interesting (particularly m2m).

I'll have to disagree with Vaughn about 1:1 relationships. They are both useful and appropriate in FMP.

Specifically, 1:1 relationships are used for optional attributes about an entity (e.g. not every employee drives a car to work so attributes about the car make, model, color, and marker plates would be stored in a separate table). They are also used for representing supertype/subtype relationships.

In supertype/subtype relationships I prefer to use the same primary key for both tables, allowing auto-create through the relationship for population of the primary key in the subtype table.

Their setup is fairly straightforward. Don't be confused by the graph though; those lines and crows feet don't necessarily represent the relationship type you see.

  • Author

Thank you to both of you for your advice. I actually do need to seperate the 2 entities into 2 tables.

It's the graph that was confusing me.

thanks again ;)

Create an account or sign in to comment

Important Information

By using this site, you agree to our Terms of Use.

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.