Calculation Issue Update (Fix Available)

Two weeks ago, we posted about an issue involving the calculation of numbers around 65,535 and 65,536.  As of today, fixes for this issue in Excel 2007 and Excel Services 2007 are available for download from the following locations:

Excel 2007: http://download.microsoft.com/download/6/1/3/61343075-aa12-4152-a761-fccc16d6cef4/office-kb943075-fullfile-x86-glb.exe
64-bit Excel Services 2007: http://download.microsoft.com/download/c/d/c/cdcccd84-86cd-4199-b01c-1df2dac66534/office-kb943076-fullfile-x64-glb.exe
32-bit Excel Services 2007: http://download.microsoft.com/download/c/d/c/cdcccd84-86cd-4199-b01c-1df2dac66534/office-kb943076-fullfile-x86-glb.exe

KB Articles have been posted as well:

Excel 2007: http://support.microsoft.com/default.aspx/kb/943075/
Excel Services 2007: http://support.microsoft.com/default.aspx/kb/943076

We are in the process of adding this fix to Microsoft Update so that it will get automatically pushed to users running Excel 2007 or Excel Services 2007.  Additionally, the fix will also be contained in the first service pack of Office 2007 when it is released (the release date for SP1 of Office 2007 has not been finalized). 

Thank you for your patience,

The Excel Team

Office Blogs Comments

Comments: (29) Collapse

  • Thanks for the update David.

  • We notices that this fix (KB943075) contains two files called excel.msp and oartconv.msp. These file names also appear in fixes KB936509 and KB934391 respectively (the file size is only bit smaller). We just wanted to confirm, if this fix KB943075 replace excel.msp and oartconv.mps files found from fixes KB936509 and KB934391? Many thanks.

  • I tried installing the Excel 2007 patch on my desktop PC, but it says:

    "The expected version of the product was not found"

    The message does not indicate what version it expected to find, or what version it did indeed find.

    Aggggh.

    R.

  • Should this fix be run when running Office 2002/2003 and using the file format converter?

  • Just out of interest: Any chance of some more information about what went wrong and how? (Overoptimized floating-point formatting?)

  • MR - You can go ahead and install the versions of excel.msp and oartconv.msp from this patch without worrying about losing previous hotfixes.  Hotfixes are 'rollups' that include all previous fixes.

    Richard - We've gotten one other report of this and are looking into the possible cause.  You may be able to solve it by uninstalling Office 2007 and reinstalling it (then apply the patch to a clean installation). If you try that, I'd like to know the results.

    SeanC - yes, if you are running the Excel converter with Excel 2002/2003, you should apply this patch, and it will update the converter.

    g - The patch is large because it contains updates for several components that use the Excel logic that showed this issue - you can see those components listed at the bottom of the KB article.  Since several of those files are large, it makes the entire patch large.

  • Just curious, since this is a calculation bug why would we need to fix the file converters?  Should Excel 2003 be doing the calculation and thus be unaffected by a calculation bug that exists in Excel 2007?  The file converters just allowe Excel 2003 to read/write the new XLSX format, right?

    Or does this bug exist in 2003 as well?

    -B-

  • "Or does this bug exist in 2003 as well?"

    I'm going to check it out right now.

  • I imagine you'd want the fix for 2003 running the converter for 2007 files. If a file comes to you in the 2007 format, and gets converted, it may not fix the error carried by the 2007 version. To my knowledge a similar bug existed in the '95 or '97 version of excel as well, but not the 2003 version.

  • It fixed one problem but left the rest 4-4.1 still give 0.0999999996 not .1

  • Is there is problem with the hotfix(KB943075)? I tried running the update and I'm getting this error:

    The installation of this package failed

    and

    A problem cuased the program to stop working correctly...

    Thanks.

  • Dan B, just for the record it wasn't I who commented on the patch size. (I asked a different question. I fear the answer is no.)

    DAnglin, that isn't anything to do with this issue, it's just the way floating-point arithmetic behaves. (The number you write down as 4.1, as represented in the computer, isn't exactly equal to 41/10.) In principle Excel could make 4-4.1 exactly equal to 0.1 by adopting (a) decimal arithmetic instead of binary or (b) exact rational arithmetic instead of floating-point, but there are plenty of other problems with both of those. Not least the fact that either would typically be an order of magnitude slower, at least.

  • g - Right, sorry about that, I was responding to 'Noticias externas.'  We're not planning to share details on this beyond what we've already communicated - i.e. that the issue occurred in formatting of floating point numbers near 65,565 and 65,536. It was code that we introduced as part of the calculation overhaul that we did for Excel 2007 however.

    Richard, BW - the one other report we got of the patch not applying correctly turned out to be due to the user having a beta version of Office 2007 SP1 installed.  The workaround is as I suggested - uninstall Office 2007 from Add\Remove Programs, reinstall from the CD, and then apply the hotfix.

  • After I tried to install the update, it shown message "The installation of this package failed".

    How to correct this problem ?

  • Will a new 2003 converter be released with the patch integrated into it?

1 2  Next >

Comments: (loading) Collapse