Microsoft KB Archive/840316

= Description of the Excel 2003 post-Service Pack 1 hotfix package: August 20, 2004 =

Article ID: 840316

Article Last Modified on 11/15/2007

-

APPLIES TO


 * Microsoft Office XP Service Pack 1

-





SUMMARY
''Microsoft has released the Microsoft Office Excel 2003 post-Service Pack 1 hotfix package for Microsoft Office Excel 2003. This article describes the following items about the hotfix package:''


 * Issues that the hotfix package fixes
 * Prerequisites for installing the hotfix package
 * Whether you must restart your computer after you install the hotfix package
 * Whether the hotfix package is replaced by any other hotfix package
 * Whether you must make any registry changes to use one or more of the hotfixes in the package
 * The files that the hotfix package contains



Article contents

 * INTRODUCTION
 * Issues that the hotfix package fixes
 * MORE INFORMATION
 * Hotfix information
 * Prerequisites
 * Restart information
 * Hotfix replacement information
 * Registry information
 * Hotfix file information
 * REFERENCES



INTRODUCTION
This article describes the Microsoft Office Excel 2003 issues that are fixed in the Microsoft Office Excel 2003 post-Service Pack 1 hotfix package that is dated August 20, 2004.

back to the top

Issues that the hotfix package fixes
This hotfix package fixes the following issues:  

817578 You cannot change a link path when an Excel Add-in is not loaded

 

829220 CMW settings are not retained by Excel 2003

 

870757 Multiple grand totals are missing after you set the Excel97Subtotals Windows registry value

839634 When you open a workbook in Excel 2003 that was created in Excel 2000 or earlier, the program may appear to stop responding



This hotfix package also fixes the following issues that were not previously documented in a Microsoft Knowledge Base article:  When you configure the Microsoft Visual Basic Applications (VBA) Workbook_Open event that targets an Excel 2003 workbook with a custom property configured, the event may not run.

 If you configure the VBA EnableSelection property programmatically, the EnableSelection property is not saved in an Excel 2003 workbook.

</li> MSQuery may insert an additional space in a SQL statement if you are connected to an Oracle database. Additionally, you may receive a syntax error when you try to modify the query.

</li> When you move or edit data labels on an Excel 2003 3-D area chart, the text in the labels may disappear.

</li>  When you programmatically create a query in MSQuery that contains a parameter query, Excel 2003 may quit unexpectedly, and you may receive the following error message:

Excel has encountered a problem and needs to close. We are sorry for the inconvenience.

If you view the details of the error message, you receive an error signature that is similar to the following: <pre class="fixed_text">Application Name Application Version  Module Name  Module Version  Offset Excel.exe        11.0.6205.0          Excel.exe    11.0.6205.0     002d2a30

</li> When you try to import data by using the Excel 2003 Data Import Wizard, Excel 2003 may incorrectly identify the code page (language setting) of the document that you are trying to import.

</li> When you use a document that contains a link that points to a Microsoft Excel workbook, the Excel taskbar button may not flash to notify you that there is a confirmation dialog box opened in Excel 2003 that requires input.

</li> If you try to move a data validation input message to you modify a cell, Excel 2003 may unexpectedly quit or stop responding, and you may receive the following error message:

Microsoft Office Excel has encountered a problem and needs to close. We are sorry for the inconvenience.

</li> When you click an option in an AutoFilter list that contains VLOOKUP function as one of the options, Excel 2003 may unexpectedly quit or stop responding. Or, the AutoFilter lists may stop functioning even though Excel 2003 still responds.

</li> When you try to send an Excel workbook by clicking the Send to mail recipient option on the File menu, the Subject box in the e-mail message is missing information if the subject contains a number sign (#) character.

</li> When you print a chart or use Print Preview, Excel 2003 may not print an attachment that contains text in a text box if the text is not set to change size with the chart.

</li> If you modify the code in a VBA module and then try to calculate a range, a custom function returns &quot;#NAME?&quot; (without the quotation marks).

</li> The Workbooks.Open method in VBA may silently fail if it is called from a worksheet function.

</li> Excel 2003 may stop responding if you use the Find and Replace feature in an array formula.

</li> The Negative Currency format in Excel 2003 is incorrect when you use the French (Canada) regional setting in Microsoft Windows XP Service Pack 1 (SP1).</li> The data that is in Excel 2003 cells that contain formulas that include the RealTimeData (RTD) function may not be refreshed as expected after you run another program. This issue occurs if the other program that you run uses timer events and passes a timer ID value to the Microsoft Windows API SetTimer function for a windowless timer. If the timer ID value is the same as the timer ID value for the windowless timer that Excel 2003 uses for the RTD function, the other program takes control of the windowless timer from Excel 2003. This action stops the RTD function from refreshing the cell data.

</li> If a signed trusted Excel add-in is loaded in Excel 2003, and the Trust all installed add-ins and templates option is disabled, the Excel add-in may not load.

</li> Excel 2003 may stop responding after you recalculate values on a worksheet by pressing SHIFT+F9.

</li> <li>You receive the following error message when you try to open an Excel 2003 worksheet while your computer is logged on to an RDP session:

File_Name.xls cannot be accessed

</li> <li>When you try to open a tab-delimited data file in Excel 2003 by using the Import Data Wizard, the spaces and the line breaks may not be displayed as expected, and miscellaneous characters may appear where the line breaks should be.

</li> <li>When you programmatically protect an Excel 2003 workbook, PivotTables may become corrupted. You may receive the following error message the next time that you try to open the file:

Unable to Read file

</li> <li>You receive the following error message if you clear merged cells programmatically and then try to paste special values in the range:

The operation requires the merged cells to be identically sized

</li></ul>

back to the top

<div class="moreinformation_section">

Service pack information
This problem was first corrected in Office 2003 Service Pack 2.

To resolve this problem, obtain the latest service pack for Office 2003. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

870924 How to obtain the latest service pack for Office 2003

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

To resolve this problem, submit a request to Microsoft Online Customer Services to obtain the hotfix. To submit an online request to obtain the hotfix, visit the following Microsoft Web site:

http://go.microsoft.com/?linkid=6294451

Note If additional issues occur or 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. To create a separate service request, visit the following Microsoft Web site:

http://support.microsoft.com/contactus/?ws=support

back to the top

Prerequisites
The following list contains prerequisites for the hotfix package: <ul> <li>The optimized version of this hotfix is a post-Office 2003 Service Pack 1 (SP1) hotfix. To install the hotfix, you must have Office 2003 SP1 installed.

For more information about Office 2003 SP1, click the following article number to view the article in the Microsoft Knowledge Base:

842532 Description of Office 2003 Service Pack 1

</li> <li>The full-file version of this hotfix is also the administrative version of this hotfix. You can install this version of the hotfix on a computer that is running Office 2003 with Microsoft Office 2003 Service Pack 1 (SP1) installed or on a computer that is running Office 2003 without Office 2003 SP1 installed. However, we have tested this hotfix more extensively on a computer that is running Office 2003 with Office 2003 SP1 installed than on a computer that is running Office 2003 without Office 2003 SP1 installed. If you install this hotfix on a computer that is running Office 2003 without Office 2003 SP1 installed, some file conflicts might occur. We support this configuration, but we do not recommend this configuration.</li></ul>

back to the top

Restart information
You do not have to restart your computer after you apply this hotfix.

back to the top

Hotfix replacement information
This hotfix is replaced by a later hotfix.

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

885845 Description of the Excel 2003 post-Service Pack 1 hotfix package: September 22, 2004

back to the top

Registry information
You must create or modify a registry key to use the one of the hotfixes that this package contains.

For more information about the registry keys that must be created or modified, click the following article number to view the article in the Microsoft Knowledge Base:

870757 Multiple grand totals are missing after you set the Excel97Subtotals Windows registry value

back to the top

Hotfix file information
This hotfix contains only those files that are required to correct the issues that this article lists. This hotfix may not contain of all the files that you must have to fully update a product to the latest build.

The global version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time tool in Control Panel.

Download information <pre class="fixed_text">  Date         Time   Version            Size    File name --  23-Aug-2004  15:29  5.0.2919.6304   5,509,664  Office2003-kb840316-glb.exe

Microsoft Windows Installer .msp file information <pre class="fixed_text">  Date         Time   Size       File name 20-Aug-2004 21:46   8,391,168  Excelff.msp 20-Aug-2004 11:44   2,123,776  Excelop.msp

After the hotfix is installed, the global version of this hotfix has the file attributes (or later file attributes) that are listed in the following table: <pre class="fixed_text">  Date         Time   Version            Size    File name --  18-Aug-2004  07:30  11.0.6400.0    10,082,496  Excel.exe

Additional notes: <ul> <li>For additional information about how to install this hotfix, see the Readme.txt file that is included in the hotfix package.</li> <li>For additional information about the differences between the two .msp files, see the &quot;Strategies for Updating Office 2003 Installations&quot; topic. To see this topic, visit the following Microsoft Web site:

http://www.microsoft.com/office/ork/updates/patch_o2k3.htm

</li></ul>

back to the top

<div class="references_section">