I've picked this syntax up from various sources on the web to generate
an MDX query. Assuming I'm using SQL 2000 and have calculated
members/measures in the cube, is there a more efficient method or less
verbose syntax?. It works fine. I'm just curious if any of the MDX
guru's out there have a better solution.

SELECT Non Empty Head({[Gender].Members*{[Measures].[Employee
Count]}},250) ON COLUMNS,
HEAD(Filter([Employees].Children, Count( Filter({Axis(0)*
{[Ethnicity].[Hispanic]}}, NOT IsEmpty(Measures.CurrentMember)))>0
),500) ON ROWS
FROM [CubeName]
WHERE [Ethnicity].[Hispanic]

In your row axis it is redundant to filter by axis(0) and [Ethnicity].
[Hispanic]. The context of the values in the cells that are returned
from an MDX query are the intersection of all the axis (including the
where clause) so the following query should be equivalent

SELECT
Non Empty Head({[Gender].Members},250) ON COLUMNS,
HEAD(Filter([Employees].Children, NOT IsEmpty
(Measures.CurrentMember)),500) ON ROWS
FROM [CubeName]
WHERE ([Ethnicity].[Hispanic],[Measures].[Employee Count])

--
Regards
Darren Gosbell - SQL Server MVP
Blog: http://www.geekswithblogs.net/darrengosbell

In article <1158174865.295655.100670 (AT) p79g2000cwp (DOT) googlegroups.com>,
shovde (AT) gmail (DOT) com says...

Thanks for the response. I removed the Slicer Axis from the filter on
the Rows axis, but I found that I still need to filter on the Columns
axis to remove empties from my results. Also, there can be more than
one Measure selected, so I cannot use it in the WHERE clause.

Filter([Employees].Children, Count( Filter(Axis(0), NOT
IsEmpty(Measures.CurrentMember)))>0)
Shane

Darren Gosbell wrote: