How can AS2005 be told to ignore “missing” member properties in calculations;
or, how can member properties be assigned to calculated dimension members?

Our AS2000 database has a calculated member (call it CM) on the MEASURES
dimension that checks a TotalsType property of dimension Z in its MDX
expression. We have also defined calculated members on dimension Z (for
example, CZ). Because CZ is a calculated member, it of course has no
TotalsType property.

Under some conditions, CM should return the value of CZ. AS2000 conveniently
ignored the fact that CZ does not have the TotalsType property, i.e., it
simply acted like TotalsType did not match any of the values we test for in
the CM calculation. The default value in the CM calculation returns CZ for
us—which is what we want.

Apparently, AS2005 handles this situation differently. In the converted
database, AS2005 fails—apparently because CZ does not have a TotalsType
property. We get an MdxScript error saying “The Z dimension attribute was
not found.”

Is there a property we can set to get AS2005 to handle properties of
calculated members like AS2000?