I'm trying to display 7 days of time clock summary data for each employee without creating 7 sets of fields and relationships. I can get the repeating values of dates by using this calculation field:

Extend ( Start Date ) + Get ( CalculationRepetitionNumber ) - 1

but I haven't found a way to use those dates in a relationship (matching dates and Employee IDs with time log records) that gets 7 calculation results, as in total hours worked for a given employee on a given day.

I know this may take a more detailed discussion, but does anyone know whether repeating fields can be used in this way at all?

I used to think repeating fields were just an ugly holdover from FileMaker's early years and should be avoided in relational design. Then it looked like maybe they provide the power of vector operations and are ideal for calendar-like or spreadsheet-like reports. I've spent hours hacking my code and searching the web for clarification.

Which is it?

Thanks for replying, erolst and philmodjunk. I ended up using 7 non-repeating date fields and 7 relationships to access the log records for each employee-day. Then I was able to get my multi-day data into a repeating field by using a

Choosefunction; e.g.,Choose ( Get ( CalculationRepetitionNumber ) - 1 ; Logs1::Total Paid Hours; Logs2::Total Paid Hours; Logs3::Total Paid Hours; Logs4::Total Paid Hours; Logs5::Total Paid Hours; Logs6::Total Paid Hours; Logs7::Total Paid Hours )

where Total Paid Hours is a calculation based on a self-join in the time-logs table.

This approach gives me the elegance that repeating fields can provide: simple calculations using

Sumand simple summaries usingTotalfor weekly and daily totals, respectively.