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.

normalizing a relationship

Featured Replies

I am trying to reduce a relationship from an inherited database. I think I have an idea, but I wanted to see what others thought.

I have table A, with two fields. The fields are E and S [A:E and A:S]. Field E has redundant names. Field S is dependent on field E, meaning that I can't have S without E. As it stands now, each record is composed of a single E and a single S. Therefore, i could say that the combination of E and S give me a primary key.

Would it be wise to break the E field into its own table (forcing a new Primiary key) and creating new tables for S. I assume that this would mean that I would have to make new relationships for S. But, I would reduce the current one table.

An I making sense?

FileMaker Version: 6

Platform: Windows XP

A, E, S? It's hard to think in these terms. Do you have real field names you can give them?

  • Author

table A can be called ASSOCIATES

field E can be called TYPE

field S can be called SUBTYPE

Thanks

Still not making sense. Try your question again with more descriptive wording.

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.