I wanted to flag jobs in a request database that are past their due dates so I created a calculation field.

If(due_date < Today, 1, 0)

Then I display the due date in red if the past due field has a 1. The client told me they need to close and reopen the database to make sure the past due jobs are displayed correctly.

If I edit due_date the calculation reflects the past due calculation correctly. For example, if I edit the due_date so it is greater then today the calculation is switched to 1. If I don't change the due_date but over time it eventually becomes greater then today, the calculation doesn't update, it remains 0.

Does this seem correct? Sounds like FMPro is working correctly.

If I were to run a script at night to correct the problem, what would be the correct action in the script? Relookup? Flush cache?

Tom

Hi,

Try using the "Status(CurrentDate)" function instead of "Today" and it should work. Also make sure your calculation field is set to "unstored".

[ June 06, 2001: Message edited by: mwiedemann ]

quote:

---

Originally posted by tbeidler:

I wanted to flag jobs in a request database that are past their due dates so I created a calculation field.

If(due_date < Today, 1, 0)

---

The Today() function has some serious limitations once you get a number of records in your database and if you plan on hosting the solution via FMServer.

Using the Status ( CurrentDate ) as an unstored calculation is a better solution, or setting a global field to Status ( CurrentDate ) if you need to use the current date in a relationship.