Search results for query: *

How did it go? I bet it wasn't a very big Pivot i.e. not many rows in the source I'm really quite interested to know how you got on because I got the same kind of message... Does anyone know the practical limits of HTML pivot tables?

How slow? How many rows? Is the cube on a local disk (faster) i.e. on the same PC or being acessed across the network (slower)? How fast is your PC? On slow PCs I have found that once the cube "warms up" it goes faster (seriously, I'm not kidding, it must be caching data locally)...

(1) surely just enter the largest value in the NULL upper_range row. (2) Given your ranges are all class intervals of 100, isn't it better to have a view on the source table that defines the Range nRange = 100*int(value/100) cRange = 1+convert(char(4),100*int(value/100)+'-'+...

Someone said upgrade to XP - thats my thinking too. Or is this posted after your previous posting? Either way to check it out I'd need to know what Excel version you're on...

I'm no MDX expert, but I'd suggest you need to consider the "dimensionality" of your fact table (details of which are scant or missing in your posting) Presumably the principal balance exists for a period of time. Does your fact table have a row for each day? or does it just change...

Use XP - I find that Excel 2000 just "feels" different (=wrong?) once you've used XP

Surely you just need to outer join the fact to the dimension table. Then any NULL in the fact table won't find a dimension row and any missing dimension row will have NULL values in the dimension columns. Having said that it can be better to use isNULL(<dimension_id>,&quot;Not Found&quot;) and...