If you're using AS 2005, there was an issue with the solve order of
query-defined calculated members always being effectively higher than
that of members defined in the cube MDX script - though functionality is
being added in SP2 to allow more flexibility:

http://download.microsoft.com/downlo...-423D-BC8F-B11
ECD4195B4/WhatsNewSQL2005SP2.htm
...
The SCOPE_ISOLATION property has been added to the MDX CREATE MEMBER
function.

This property enables session-scoped and query-defined calculations to
be resolved before calculations in the cube rather than after.
However, you might also be able to get [All Other] to resolve before
[Std Margin %] by using Aggregate():

Member [Customers].[All Other] as
Aggregate([Customers].[Customers].Members - [TopSet])


- Deepak

Deepak Puri
Microsoft MVP - SQL Server

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

Thank you, Deepak. Yes, we are currently calculating All Other by the method
you described below, however performance is not the best (we have some big
dimensions with lots of members).

I will wait for SP2 to come out.

Steve

"Deepak Puri" wrote: