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.

No showing updated expiration date

Featured Replies

Hi All

I have a program in FM8.5 that keeps track of our welders qualification. The welders are required to weld at least once in a six month peroid for specification reasons so we have a continunity log for each welder. Once a month someone from the Quality Control department prints a report of welders that need to be update. The problem is that sometimes one person might update the log without that telling anyone and then went someone else updates the log a couple days later than we have two updated records within a couple of days from each other and I would like to not have this occurence in the DB.

The simplest way would be once the record has been upddate then is would not be listed in the "to be update" portion of the continunity log for that month. To find welders that needs to be update in the month of december, The script is as folows

Enter Find mode

Set field ( expiration date, 11-30-2008 .. 12-30-2008)

preform find

This works but it will show that a welder needs to be update for December if the continunity log portion of the DB is run again regards if a update record is in the DB.

How do I just show the records that need to be update and not show those that have been update if someone should preform the update task twice in one month.

I hope I explain it so it makes sense to your.

Thanks for all your help in the past and in the future.

Lionel

How is expiration date calculated?

If I were to set this up, I'd have a table for Welders and a relationship to the log table. The log table would store, among other data, the date of last welding job. In the welders table, I would calc the expiration date (unstored) by adding 6 months to this last welding job.

If you have two log records for the welder, wouldn't they have the same info? Sounds like the interface to the log file should change to let a person know that it was already done. Can't they see the previous log records for that welder?

Then, it's just a matter of Finding on welders whose expiration date is btw the dates specified, as you do.

So, sounds like your expiration date isn't calculating correctly.

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.