Hi Yolanda,

Based on your problem description, one solution will be to create 2 cube
"sum" measures, rather than calculated measures, based on SQL
expressions like:

For order amount:

case when coalesce([Proceed].[Trip No.], '') = ''
then [Proceed].[Amount] else 0 end

For trip amount:

case when coalesce([Proceed].[Trip No.], '') <> ''
then [Proceed].[Amount] else 0 end


If you're using AS 2000, then these expressions can be added in a view,
or as the measure's "Source Column". WIth AS 2005, they can be addes as
Named Calculations.

- Deepak

Deepak Puri
Microsoft MVP - SQL Server

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

There are many factors affecting cube processing time, so it's hard to
say without knowing more details. If you're using AS 2000 with many
dimensions, then cube schema optimization (which requires dimensions to
be shared) is highly recommended.


- Deepak

Deepak Puri
Microsoft MVP - SQL Server

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