This is pretty close.

I have the function already, but it is just a manually created SQL
string. Since the user might want to see as few as 2 consecutive
quarters, or as many as 8 consecutive quarters, I have manually
created the SQL strings for each possibility.

I was hoping with a for/next loop, the function could see how many
quarters the user wants to see (passed in as a variable), and then
loop through the possibilities, building the SQL string on the fly ((1
and 2) or (2 and 3)). This way I would have to maintain a lot less
code in the event of requirements changes.

On Jul 28, 2:22*pm, Icarus <tjmos... (AT) gmail (DOT) com> wrote:
Sounds like a hellatiously long where clause.

I wonder if a (keyword) UNIQUE SQL statement would be of any merit.
It seems that'd be a simple For I.For J loop, especially if you can
increment the dates so you can get the field names of the quarters.