Well, what if you could upgrade to AS 2005...

http://sqljunkies.com/WebLog/mosha/a...iselect_friend
ly_mdx.aspx

One very common problem with authoring MDX calculations historically has
been the behavior of these calculations when the user who browses the
cube selects multiple members in the slicer as opposed to single one. Of
course this functionality (usually called multiselect) is present in all
of the major AS client tools - Excel, OWC, Panorama, Proclarity, various
Excel Add-Ins, Data Analyzer etc. It often happens that MDX calculations
which work fine in single member slice mode don't work that well when
multiselect is used, or do work with multiselect by some dimensions, but
not by others. The problems manifest themselves either as cell errors,
or, worse, as wrong (i.e. non-intended) results. This problem is common,
yet, to the best of my knowledge, it has not been addressed before. So
calculation authors are left struggling to resolve it, and usual
resolution is to ignore the problem, and hope that users won't do
multiselect over offending dimensions. In this article I will try to
address some of the typical scenarios where this problem can occur and
recommend possible approaches for solution. I will use Foodmart 2000
database for examples, but most of the content applies to Analysis
Services 2005 only.
...

- Deepak

Deepak Puri
Microsoft MVP - SQL Server

*** Sent via Developersdex http://www.developersdex.com ***

This NG thread from last year discussed a couple of AS 2000 approaches,
depending on whether Enterprise or Standard Edition is used:

http://groups.google.com/group/micro...olap/browse_fr
m/thread/282b36a2782d65b6/e831d00a418990a1#e831d00a418990a1
the
filter (in OCW Pivottable manually) on time dimension (eg. only Quarters
Q1,
Q2, Q3 in 2004). This applies to Previous Year Values calculated via:
([MEASURES].[Sales], ParalellPeriode([TIME].[YEAR],1))
...

- Deepak

Deepak Puri
Microsoft MVP - SQL Server

*** Sent via Developersdex http://www.developersdex.com ***