sHi all,

I'm encountering some odd Cube behavior using Scope. I have a cube which
processes fine. After adding the following (I believe simple test scope
command) the cube no longer processes. Furthermore, when I remove the mdx,
the cube continues to no longer process. It is not until I shut down my
solution and re-open it (without the Scope) that the cube again can process.

My questions are 1) Does scope need to be in a specific spot in an MDX
script i.e. at the beginning/end. 2) if at the end, does it need a calculate
statement afterwards. 3) Does the Scope command need to be attached to a
create member?

Here is my simple text

SCOPE
([Dim Driver].[Driver Lev 1].&[Utilization Down],
[Measures].[Units]
);
This = 0;
END Scope;

Thanks in advance!

Mark

Hi Mark,

What error message do you get when you process? Your SCOPE statement looks
ok to me; so long as it comes after the CALCULATE statement in your script it
*should* work. To be honest if you need to open and close VS to get the cube
to process then it sounds like it might be a bug to me...

Regardsm

Chris
--
I blog about Microsoft BI here:
http://spaces.msn.com/cwebbbi/
Do you need help with Analysis Services or MDX? I''m available for hire:
http://www.crossjoin.co.uk/


"MarkFrank" wrote: