April 24, 2003 at 6:57 am
I have a set of Excel pivot tables that point to Analysis Services OLAP cubes (SQL2K/SP2)which have been working fine for months. These tables typically have several fields in the "page" area. Users have recently noticed that when they try to drag one of these fields into the "row" area of the table, they often turn into one of the OTHER fields that was also in the "page" area. When they try to drag the unintended field back into the "page" area - or even out of the table - they get an error that you usually get when you try to use a field that has more than 64K unique values...(even though none of these fields have even close to that). Any other action after this error also produces the same error. They basically have to close down Excel and restart. The error does not appear to happen if you open a fresh connection to the AS cube and rebuild the table. But save it for later use, and after a few uses, the error begins to show it self again. This sounds like a client problem, but it didn't seem to show up until sometime after SP2. Reinstalling Excel has not solved the problem and with all the problems I'm hearing about SP3 and AS, I'm not sure I'm ready to go there yet. Has anyone else experienced this problem?
April 24, 2003 at 8:34 am
Have you tried reinstalling pts(lite) on the client? Also, have you thought about installing SP3 for AS?
Michael Weiss
Michael Weiss
April 24, 2003 at 11:47 am
Seen the problem, don't know of the solution but as a workaround if you use the show field list toolbox and drag a field from there to the row. You will get the expected field
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply