I have a database consisting of records relating to activity: timeslips.

The records are used to prepare time based invoices.

I Have a separate database with a single index field which I have related to timeslips using the index field. I have a portal using that relationship which is filtered so that I can see the values of records enteRed in the last 7 days. This is then summed.

I am sure there is a less cumbersome way to know from moment to moment how much work I've done in the last 7 days....

I am sure there is a less cumbersome way to know from moment to moment how much work I've done in the last 7 days....

I don't even understand the "cumbersome" way you describe. I think you could either find the records by their date, or define a relationship along the lines of:

AnyTable::cToday ≥ Timeslips::Date

AND

AnyTable::cWeekAgo < Timeslips::Date

where cToday is an unstored calculation field = Get (CurrentDate) and cWeekAgo = cToday - 7.

I don't even understand the "cumbersome" way you describe. I think you could either find the records by their date, or define a relationship along the lines of:

AnyTable::cToday ≥ Timeslips::Date

AND

AnyTable::cWeekAgo &lt; Timeslips::Date

where cToday is an unstored calculation field = Get (CurrentDate) and cWeekAgo = cToday - 7.

That's effectively what I've done.

Can it not be done within timeslips?

What do you mean by "within timeslips"?