MSDN for SSAS would be a good place for you to start.

correct, you can export to csv and then import into Excel 2007 or 2010. However, you lose your formatting and any grouping / show / hide functionality

Phil Parkin (9/30/2011)

---

Scott Murray-240410 (9/30/2011)

---

We often see this error when the export exceeds the 56k rows; unfortunately, the export still uses the Excel 2003 limits and the error is...

We often see this error when the export exceeds the 56k rows; unfortunately, the export still uses the Excel 2003 limits and the error is never clear that the...

It sounds like you need to check the detail level and relationships in the model. Also check to see if you can drill down from the fact table; ...

You likely need discretion buckets to group the attributes into groups. You can create your own or let SSAS do it.

The dimension attributes should be in your date dimension. Using the Date Dimension, you would want to select Qtr, Month, Year. Maybe sure you setup the relationship between...

Have you verified the page sizes?

You could create a parameter flag that controls the visibility of column. Then that flag could be updated to not show when wanting to export to pdf.

William Pearson writes several excellent article on SSAS and MDX.

Check out these links:

SQL Server Central Stairway Series[/url]

Database Journal Series

You can also use the document map properties.

Unfortunately many bosses like Long Work..... I can hear them now... so and so was here until 3.00am. Not recognizing that so and so surfed the net...

The only downside I see with using stored procedures is when you want to pass a multi-value filter as a parameter. In that case you need to parse out...

Have you checked the InteractiveSize on the Report Properties as compared to the PageSize Property of the Report (not the body object).

Have you tried exporting to CSV and then opening the CSV in Excel.