Skip 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.

Lookup problem

Featured Replies

  • Newbies

I have two DBs that are happily related. However, DB "A" will not lookup a corresponding field in DB "B". Both are text fields, so there is not a compatibility problem. I have followed Hoyle's rules a dozen times and it just doesn't work. I am a FM 6.0 newbie, so I'm figuring it's me or a problem when I installed the software. When I try to "relookup" the field, it tells me there is no corresponding field in the related DB, even though I have established the link. Help!!! It's driving me crazy.

Hi, EPad3. Is the field on the right side of the relationship indexed? There are certain conditions that cause a field not to be indexable. Go into that field's options, and try to turn indexing on. If you can't, that's probably your issue. If you can, or if it's already on, could you give us an example of data you expect to match that doesn't?

Jerry

Also...check that the field you're in when triggering the relookup is the key rather than the source or target fields.

  • Author
  • Newbies

I made sure the field was indexed, but still no joy. Here's what I did: I established a relationship between DB "A" and DB "B" and tested it, so I know the relationship works. I then established a text field "Caption" in DB "A" and specified a text field in DB "B" (also named caption) for a lookup target. I made sure that the target field in DB "B" was indexed. When I attempt to "relookup" the field in DB "A" I get an error message that reads: "There are no fields that lookup values based on the field "Caption." I'm stumped.

Just to be clear... what you want is for DBA::Caption to be filled with data from DBB::Caption? If so, then you would have to perform the re-lookup on the key field in DBA (that is, whatever field is on the left side of the established relationship), NOT on Caption.

J

  • Author
  • Newbies

Yes, that's what I did. I did the relookup on the field in DBA::Caption. The two fields in the two DBs just happen to be named the same...could that be a problem?

DO NOT do the re-lookup on DBA::Caption. Do it on the KEY field.

The key field is the field you've used to build your relationship. So if the relationship is from IDnumber in DBA to IDnumber in DBB, the key field is IDnumber in DBA (to write it in Filemaker terms, DBA::IDnumber). Since the key field is DBA::IDnumber, you need to click into THAT field and do the re-lookup.

To reiterate, DO NOT do the re-lookup on the field Caption in the file DBA.

J

  • Author
  • Newbies

EUREKA!!!! Finally! Thanks so much. I am saved. I can go back to regular mealtimes and cancel my next therapy session.

Create an account or sign in to comment

Important Information

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

Account

Navigation

Search

Search

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.