XL2000: OLAP Data in Excel PivotTable Is Incorrect

This article was previously published under Q268079
This article has been archived. It is offered "as is" and will no longer be updated.
SYMPTOMS
In Excel 2000, when you create a PivotTable that uses an Online Analytical Processing (OLAP) cube as the data source, the data for one or more levels is incorrect.
CAUSE
Excel allocates an internal 253-character buffer for a "unique member name," an internal entity which Excel receives from Microsoft SQL Server. The OLE Database Connectivity for On-Line Analytical Processing (OLE DB for OLAP) specification states that unique member names may be as long as 2,048 characters; however, Excel truncates a unique member name after 253 characters.

A unique member name is similar to a key. It is a crucial entity that Excel uses to communicate with the SQL Server. The truncation of a unique member name usually results in an error. However, in some cases the truncated name may match another name that already exists, and Excel then displays incorrect data.
WORKAROUND
To work around this problem, limit unique member names to 253 characters or fewer.
The hotfix changes the behavior of Excel in the scenario that is described in the "Cause" section. Instead of displaying incorrect data, Excel displays #N/A to indicate that the data for the cell is invalid. The hotfix does not correct the underlying problem of Excel displaying incorrect data.
STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.

This problem was first corrected in Microsoft Office 2000 Service Pack 3 (SP-3).
MORE INFORMATION
For information about Object Linking and Embedding for Databases (OLEDB), please visit the following Microsoft Web site:
excel2000 xl2000 olap oledb cube pivottable incorrect uniquemembername online
Properties

Article ID: 268079 - Last Review: 10/20/2013 23:15:15 - Revision: 3.3

Microsoft Excel 2000 Standard Edition

  • kbnosurvey kbarchive kbhotfixserver kbqfe kbfix kboffice2000sp3fix kbbug KB268079
Feedback