Hi,

According to this post:

http://groups.google.com/group/micro...c3f80322478058

calculated members defined on the cube are always evaluated before those
defined in a query, regardless of what their solve_order property is set to.
There are some circumstances where this can be a problem: eg, in one of our
cubes we have a Scenario dimension with Actual and Model members. We also
created a calculated member for the dimension called Variance, which is
simply [Scenario].[Actual] - [Scenario].[Model]. However, this member
sometimes gives incorrect results if it isn't the last calculation to be
evaluated, therefore we set its solve_order to 999.

Unfortunately, it's still evaluated before query-defined calculated members
regardless of what solve_order we define for it. As a result we're limited
to creating all our calculated members on the cube, which is not ideal.

Can one of the Microsoft people tell me whether this issue is being
addressed?

Thanks,

Peter

Yes this is still true.

As for the future, it is to early to tell...

"Peter Kenyon" wrote: