1 of 1 people found this helpful
your get(currentdate) calculated field is evidently stored. If it is on the "left side" of the relationship, you can make it an unstored calc, and then it will always be correct.
Thanks, Peter. Good to know for future reference, but unfortunately I need it to be on the "target" side of the relationship, so only future items are visible from the point of view of the item to be reserved (the "archer" side).
This is equivalent to the old "Today" function in Filemaker <= 6.
Short term option here is to have that field as a simple stored date field, and a startup script that populates that field with today's date the first time the database is opened each day.
This is quick and simple until your database grows to large numbers of records. At that time the morning calculation will start taking considerable time. The long term fix is to think about the structure and figure out a way to have the unstored current date on the left side of the relationship.
Richard S. Russell wrote:
unfortunately I need it to be on the "target" side of the relationship, so only future items are visible from the point of view of the item to be reserved
Why don't you make the relationship:
Items::ItemID = Reservations::ItemID
Items::cToday < Reservations::DueDate
where Items::cToday is an unstored calculation = Get (CurrentDate).
Peter gets the "Helpful Answer" award for providing the correct concept.
Michael gets the "Correct Answer" award for providing the actual formula to make it happen.
Thanks, guys. This works just slick!