Hi all,

I have AS SP3 and a virtual cube that is made up by 2
actual cubes. One actual cube is getting data from the
Actual Fact table, and one is getting data from the Budget
Fact table.

The actual cube for the Actual Fact table has multiple
partitions, ie. split by month (ie. related to the a
period key on the Actual Fact Table). The actual cube for
the Budget Fact table has only one partition by default.

I don't have any problem drillthrough on the Virtual cube
from AS as data is returned from both actual cubes.

But when using the ADO recorset (msado26.tbl) to
drillthrough the MDX Select,
ie. DRILLTHROUGH MAXROWS 100 SELECT {[Measures].
[Chargeable Hours PTD]} ON COLUMNS, {[Engagement Partner].
[All Partner]} ON ROWS FROM [Engagement Partner
Performance] WHERE ([Currency Type].[Global : USD],
[Engagement].[All Engagement], [Period].[2002 - 08])

Only measure that is coming from the default partitioned
cube can return data. Am empty recordset is returned when
the measure is coming from the multiple partitioned cube.

When I remove the partitioning by months and reset to the
default partition then drillthrough using ADO recorset
works.

Is it a known problem?
Any suggestions from anyone out there??

Any comments is appreciated as I've been looking at this
problem for ages already...

Thanks & Regards,
Dao Trinh

For any one that is interested on a solution ...
When performing the drillthrough with ADO be aware to loop
through the recordsets with rec.nextrecordset ...
Regards,
Dao.

This is by-design. Drill-through returns a resultset with multiple rowsets
and you need to design your application around that.
If you search the archives of the newsgroup, you will find several postings
on this topic.
--
Dave Wickert [MSFT]
dwickert (AT) online (DOT) microsoft.com
Program Manager
BI Practices Team
SQL BI Product Unit (Analysis Services)
--
This posting is provided "AS IS" with no warranties, and confers no rights.

"Dao Trinh" <dao.trinh (AT) solution6 (DOT) com> wrote