Interesting... I've come across a function called VisualTotals(), but not sure it could meet my needs. Never used it so I'm not sure what it can/can't do or quirks it may...

Some additional clarification:

I'm trying to create a calculated member in AS that computes a geometric mean; not trying to use mdx in excel vba. Only way to accomplish this, I think, is...

Huh -- interesting...

Yup, putting the time dimension into the pages area of the excel pivot yielded correct results.

Here's excel's mdx:

SELECT NON EMPTY HIERARCHIZE(AddCalculatedMembers({DrillDownLevelTop({[PROCEDURES].[All PROCEDURES]}, 10, , [Measures].[CasesYTD])})) DIMENSION PROPERTIES PARENT_UNIQUE_NAME...

Steve,

(thanks for sticking with me on this...) Yes, I've specified in the pivot table that descending order be performed on the calculated member (CasesYTD), and that it identify the Top...

Steve,

Thanks for the reply -- but still have problems. The Excel pivot table is directly querying the external olap data (using the pivot table wizard), so I don't write any...

I ran into a similar problem with XP; couldn't connect to analysis services at all. The fix for me was to install the latest sql server patch (3a?). With the...

Steve:

Thanks for the reply. I actually figured it out on my own. My problem was with syntax. (I have Spofford's book, but his examples for Filter were data bound without...

Great suggestions! Many thanks. (I didn't think the solution would be difficult, but my brain seems to still be on holiday.)

--Pete

I've actually got the code trimmed down: i.e., If..Thens has been deleted.

Here's a cleaner expression:

SUM(Crossjoin(Ytd([START_TIME),{[END_TIME].CURRENTMEMBER.LEVEL.MEMBERS.ITEM(0):[END_TIME]}),[Measures].[CASES])

The above mdx efficiently/accurrately crossjoins YTD(start_time) with a set that covers the first member at any...

Steve:

Your recent suggestion is exactly where I ended up the other day - amazing. (Eventhough I'm new to mdx, I'm glad I can keep up with a pro like yourself.)...

Steve:

Your suggestion almost works for me:

sum(CROSSJOIN(Ytd([START_TIME]), Ytd([END_TIME])),[Measures].[cases])

Perhaps, though you can suggest the correct "tweek" it needs...

The limitation of the above expression is that the YTD function always stays limited...

Never mind this post. I discovered that the DBA misdefined the unique member ID for one of the time dimensions to just 'month' -- consequently, the linkmember function only linked...

Steve:

Interesting ideas as alternative solutions. They may prove better than mdx! Even so, I'd still be thrilled to know what the mdx solution is to my problem. I find mdx...