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.

Dates and relationships

Featured Replies

I'm having a little trouble with a database. The database is used to keep track of items that need to be sent out every so often and calibrated. I have a status field that can be any of the following,

OK - Means the item is ok to use

Send for Calibration - means the item is ok to use but is getting close to expireing and needs to be sent out for calibration.

Expired - Means the item cannot be used

So I have a field called Expired flag that is set to 1 if the host date is greater then the expiration date else 0, and due for cal flag that is set to one if the host date is greater than the due for cal date else 0

I also have a field that is set to 1 for every record I call 1key.

Here is my problem: I set up an instance of the table for each of these statuses. The relationship is expired flag = 1key and due for cal = 1key. I did this to have tabs showing the items for the various statuses using portals. It seemed to work ok but I realized it was not updating my tabs. This was of coarse because the calculations were set set to store the results.

So begins the trial and error phase. If I set the two status flag calculation fields to not store the results nothing shows up in my portals. Same is true if have today field to handle just the host date as a calculation and use that field in my status calcs because the status calc automatically sets its self not store the results and nothing shows up in my portals. I tried to use a global date field that I would set each time the database is open but If I used a global field again the status calcs set themselves to not store the results and nothing shows up in the portals. I didn’t want to have to set a today field for every record so I tried putting it in its own single record table but if I use a related record in the status calc fields it also sets to not store results.

Any suggestions?

You need to move the unstored part to the parent side of the relationship. For example, a relationship defined as:

Parent::cToday > Child::ExpirationDate

(where cToday is an ustored calculation of current date) will show all children past their expiration date.

  • Author

Thank you, I'll try that :o

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.