Thank you everyone. All your answers helped me with my question. The reason I was not able to just parameterize the date and quarter to solve the entire problem is because the column names often vary each quarter, even when most of them mean the same thing as the last quarter. I have asked a few times if the people who pull the raw data could use a consistent naming scheme but they won't. They always come back with: The measures may change from quarter to quarter, to which I reply: Any new measures are fine; I can add or subtract measures. But I'm hoping that the measures that stay the same from quarter to quarter can have the same names. Answer is no.

So, for example, we have a measure that was called [Long measure name with lots of spaces and chopped off names ] one quarter and the same measure will be called [ Long measure name with lots of spaces and chopped off nam ] the next quarter. Note too the extra spaces in one. And there are many, many files, measures, etc. It's a nightmare. My coworkers are not database clueful but believe they are because they don't know what they don't know. I asked the smartest one how he would define a data warehouse versus a "regular" database. His reply: A DW is just a really, really big database. I said the way data is stored varies, for one thing. And this person is very intelligent but the rest are not so much. Majority rule where I work.

I suppose I could look into parameterizing the column names too....

Thanks again everyone!