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.

Featured Replies

I was having a discussion the other day with another in house developer over the context of lookups.

Here is the scenario:

tables: Customers, Contacts.

Relationships

Customers::Customer_ID(Base Table) = Contacts::Customer_ID(Table Occurrance)

If there is a lookup that we need to do in Contacts(say, a default value for a toll free phone number)

Is the correct way to do it:

A) In the lookup dialog set the "Starting with table:" option to the Table Occurrance of contacts, looking back to Customers.

OR

B) Create a new relationship Contacts::Customer_ID(Base Table) = Customers::Customer_ID(Table Occurrance). then make the "Starting with table:" option Contacts, looking over the new relationship to Customers?

I argued that option B was correct, because it was more logical, and although this is a very simple scenario, I think that option A makes it harder to maintain/troubleshoot issues.

Plus(being somewhat obsessive about this stuff) I think it looks sloppy.

Anybody have any other thoughts?

The first scenario is the better choice (between the two options you've given); when from Contacts, you want to look up a toll free number in Customers, you use the same primary relationship. Why create another DUPLICATE relationship when unnecessary?

But even further ... why are you wasting another field in Contacts which holds the toll free number when it is already in Customers? The ONLY reason you might want the number actually planted as static data in Contacts, is if the number might change and it is important to keep the original number (for audit and back-track purposes). But the Contacts should always only display the Company's CURRENT toll free number anyway, right?

So just take the Company's toll free number and plop it on the Contacts layout. In this way, it will display for all of that Company's Contacts AND, if the Company toll free number changes, it will automatically change for all of their Contacts (because it is the Company number anyway).

LaRetta :wink2:

I don't get this "Base Table" vs. "Table Occurrence" thing. Is this something to do with anchor/buoy? Going by your TO names alone, the "new" relationship already exists.

I agree with LaRetta regarding the lookup seeming unnecessary.

  • 1 month later...
  • Author

you are right, the example(toll free number) given was bad.. and in the solution I was looking at, we do it the way Laretta suggested.

It was just the first field I saw on my other screen when I was typing the question.

My question was more hypothetical than anything.

thanks for the feedback guys!

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.