BUG: Calculated Members Based on User Defined or MS Excel/VBA Functions Do Not Work when Accessed from Excel and Pivot Table Controls

ID: Q238306

The information in this article applies to:

Microsoft SQL Server OLAP Services version 7.0

BUG #: 1350 (plato7x)

SYMPTOMS

Calculated members based on user-defined functions (UDFs) and Microsoft Excel or VBA functions do not work when accessed from Excel 2000, Office 2000 pivot table controls, or other clients that execute queries asynchronously.

If calculated members in a cube are based on Excel functions, VBA functions, or user-defined functions, the user is not able to gain access to these calculated members mentioned before, or gets an error message, such as:

An error occurred during attempt to get a cell value. Problem occurred.

CAUSE

This problem occurs whenever the client executes asynchronous queries involving a calculated member based on a user-defined, Excel, or VBA function.

RESOLUTION

A supported fix that corrects this problem is now available from Microsoft, but it has not been fully regression tested and should be applied only to systems experiencing this specific problem. If you are not severely affected by this specific problem, Microsoft recommends that you wait for the next SQL Server service pack that contains this fix.

To resolve this problem immediately, contact Microsoft Product Support Services to obtain the fix. For a complete list of Microsoft Product Support Services phone numbers and information on support costs, please go to the following address on the World Wide Web:

http://www.microsoft.com/support/supportnet/overview/overview.asp

The English version of this fix should have the following file attributes or later:


   Date      Time    Version    Size    File name      Platform
   -----------------------------------------------------------
   07/27/99            7.0      41 MB   s700706i.exe   Intel

NOTE: Due to file dependencies, the most recent hotfix or feature that contains the above files might also contain additional files.

WORKAROUND

The workaround is as follows:

If a new application is being developed, then this problem can be avoided by executing the queries synchronously or writing the user-defined functions as free-threaded.

If Excel or Office Web components are used to access data, then equivalent MDX expressions (if available) can be used instead of the user-defined, Excel, or VBA functions.

STATUS

Microsoft has confirmed this to be a problem in SQL Server OLAP Services version 7.0.

Additional query words:

Keywords : kbSQLServ kbSQLServ700
Version : winnt:7.0
Platform : winnt
Issue type : kbbug