Description of the Excel 2003 hotfix package (Excel.msp): December 16, 2008

This article describes the Microsoft Office Excel 2003 issues that are fixed in the hotfix package that is dated December 16, 2008.

This hotfix fixes the following issues that were not previously documented in a Microsoft Knowledge Base article:

• Consider the following scenario:
  • You have a pivot table in Excel 2003 that queries data from a Microsoft SQL Server database.
  • You restore a database that has identical fields and structures as the existing database.
  • You update the pivot table against the newly restored database.
  In this scenario, Excel 2003 switches the dimension members of the pivot table page fields.
  
  
• When you print multiple copies of an Excel 2003 file, the Collate setting is ignored. This problem occurs when the file is configured to print across multiple pages.
  
  
• You copy a named range from an Excel 2003 Service Pack 3 (SP3) worksheet. Then, you use the Paste Special feature to paste the range as an Excel Workbook Object link into an Office 2003 application, such as Word 2003 or PowerPoint 2003. In this scenario, the link reference does not contain the range name. This problem occurs if the name of the worksheet has a space.
  
  
• You develop a user-defined function in an Excel-link library (XLL) to retrieve real-time data. When the function is called from an array formula in Excel 2003, you receive a "#VALUE" error message.
  
  Note This problem does not occur when the function is called from a single cell in Excel 2003.
  
  

Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problems that are described in this article. Apply this hotfix only to systems that are experiencing the problems described in this article. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site: Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites

There are no prerequisites for installing this hotfix.

Restart requirement

You do not have to restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace a previously released hotfix.

Registry information

To use one of the hotfixes in this package, you do not have to make any changes to the registry.

File information

This hotfix may not contain all the files that you must have to fully update a product to the latest build. This hotfix contains only the files that you must have to correct the issues that are listed in this article.

The global version of this hotfix package uses a Microsoft Windows Installer package to install the hotfix package. The dates and the times for these files are listed in Coordinated Universal Time (UTC) in the following table. When you view the file information, the date is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.

Download information



Microsoft Windows Installer .msp file information



Excel.msp information

For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base: