In AS2K --

I have a ReviewRound dimension and each member of this dimension has two
attributes, a start and end date.

Using a calculated member, I determine whether the ReviewRound was active
during a given date range determined by the current member of the Time
dimension. When a user selects any member from this dimension, the
calculated member checks to see whether the ReviewRound was active for *any*
day in the period. For example, I have a ReviewRound active from 2006-01-01
to 2006-04-03. The user selects [Time].[2006].[April] and the calculated
member sees that it was active for three days in April, so it outputs this
number as the expression.

The problem is that when the ReviewRound dimension is added to a cube where
there are other dimensions, the formula has to be updated to handle every
possible combination of slice and dice for the other dimensions present.
This becomes impossible to write, test and maintain. Ideally, it seems like
it should be stored in a fact table in the data mart, but you still end up
with the problem of how to deal with ranges that overlap the Time dimension.

Does anyone have any good links to articles explaining how to handle
calculated members that use date ranges in MS OLAP?

Thanks in advance,

Ian