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.

FMP6 to FMP7 relationship malfunction

Featured Replies

I have an appt program that was recently upgraded from FMP6 to FMP7. Since the upgrade, the calculation of Initial and Follow-up appt times does not work.

in FMP6, whenever an Initial or Follow-up appointment is scheduled, FileMaker is creating an entry in either the Iappointments or Fappointments table. Part of the data in each of these records is the InitialDate or FollowDate, along with the PatientRecord number.

IN FMP7, the unit of this program that seems to be failing is the MatchFieldForShowInfo.c field.

A patient whose record# is “10-3157” and schedules an appointment on “08-09-2005” should have a resulting MatchFieldForShowInfo.c field calculated to “103157892005”. This information is used to connect a relationship with a similarly calculated field in the DrGood.fp7 database

If everything worked as it should in FMP7, then a ‘Find’ operation (using the Find_script) would find all related records in the Iappointments and Fappointments databases, toggle over to display all records matching the request, and display related information (based on the matching relationship of the MatchFieldForShowInfo.c field).

Unfortunately the calculation in the database (GetAsNumber(RecordNumber) & GetAsNumber(gFindDate.g) works unreliably, creating unpredictable results, thereby nullifying the possibility of a match, or worse, generating an unexpected match.

Someone has advised the following:

"To solve the problem will require replacing the core of the relationship underpinnings in your system"

is this true?

how would it be done?

is there a more reasonable solution?

is there a way to easily fix this?

any ideas?

Thank you.

In FM 7, relationships can have multiple criteria, so there's no need to use compound keys (concatenated keys).

Replacing your relationships using FM7's new scheme is more effort in the short term, but it'll make the databases more flexible and easier to support. Plus you'll learn about 7 which is so much more powerful than 6!

  • Author

I resolved this problem successfully. It had nothing to do with the relationships..

Edited by Guest

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.