That would be
YourTable::yourTimeField - GetNthRecord ( YourTable::yourTimeField ; Get ( RecordNumber ) - 1 )
is it possible that this does not take into account the sort order of the table relationship? It appears to work with records that i have created consecutively but not when they are entered out of time order
If the calc is unstored, it will reflect the current sort order. If it is stored, it will be record creation. The downside to the field being unstored is slower performance when viewing that field in list or table view.
David Jondreau wrote:
The downside to the field being unstored is slower performance when viewing that field in list or table view.
Right; unstored calc fields are those you don't want to have on a List layout for a table with 1,000,00 records where you select ”Show All Records” …
But with, say, a found set of Schedule records for one day, or even a week/month, the impact shouldn't be noticeable (depending on your activity frequency).