>What about "Multiplier"? Does OPERATOR_CLASS table also has date field?

OK, we're after the averag no. of journeys in the ETMDATA (Automated Ticket M/c DATA)say the pensioner bought a return ticket, (a particular class), that class's multiplier might be 2.0, meanimng that ticket is worth 2 trips. An all-day-rover (class) might be used, on average, 2.5 trips.

This only applies to last year's data. Now as they're all zero-rated, all classes have a multiplier of 1.0.

Very astute of you to divine that the Op. Class table has a date. Actually it has a start and end date, specifying when the conc. scheme began and ends. But that isn't important here as that's dealt with in the pre-processing of the raw ETM data that gets compiled into out ETMDATA table that sums up ticket sales for each ticket class within each route.

Confused? I know I am! ;-S

>
>>Sorry, I'd assumed the date bit would be the easy bit, even for me

(where date >= ... and date <= ...)

Of course, as ETMDATA is records by the day, each rec has a date field too. And all the transactions are summed for their dates within the period(s).
>>
>>Cheers
>>
>>Terry
>>
>>>Hi Terry,
>>>
>>>Not a single your table has a date field. How do you get Period1/2 w/o it for "No. tickets" and "Multiplier"?
>>>
...