Reply to thread

Message: [QUOTE="Michel Walsh, post: 11437296"] The GROUP and the ON clauses should describe the unique ordering sequence, without dup. In fact, you should be able to describe the sequence, exactly, just by its data (not by its 'position' in the table) to be able to get a basic solution based on SQL. Note that I assumed oderDate was a date_time field (not a string), so it may be possible to have a day (in addition to a year and a month), or even a time in it, and with that such precision, {team, orderDate} can be a valid primary key candidate (or at least, we could define a UNIQUE constraint on it). ONCE the running sum is computed, you can then FORMAT that full date_time value to only show the year and the month, but do it only AFTER having computed the running sum. Is that possible, in your case? Vanderghast, Access MVP [/QUOTE]