Microsoft Excel

PingBack from http://microsoft.whitewitty.info/?p=4926

Thanks for the update David.

Two fixes came online today for an error in the display of calculation results in Excel 2007 and Excel...

via MSDN Excel Team blog Excel 2007を持ってな...

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?

Hace un par de semanas os coemntabamos un fallo de excel 2007. Pues bien, parece que tras un breve testeo Micrososft ya ha lanzado el parche que corrige esos errores de cálculo con un tamaño ni mas ni menos que de 32 MB. Si te encontrabas afectado po

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

Its an important update but size of the update ~33Mb. Why? What are the things it updated? "Two

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.

Please check out David's post for links to the fixes. http://blogs.msdn.com/excel/archive/2007/10/09/calculation-issue-update-fix-available.asp

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 ?

Don't dilly-dally, make sure you rush to get the crucial, gaping-hole fixer Excel patch for the rounding

Sarà difficile spiegarlo a chi non è tecnico, ma è un dato di fatto che l'unico programma senza bug

Pochi giorni fa ho segnalato un bug di Excel 2007 , all'interno di un post dove parlavo più in generale

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

Thanks for the update but are you sure that other office apps like MS Access are safe enough with such kind of bugs ? There's huge database calculations running in servers.

If Microsoft doesnt disclose what they have learned about the cause of the bug then they are dismissing the opportunity to let the emense staff in the foggy Computer World help them as they have in probably millions if not hundreds of millions of cases in the past. The SYA strategy is not cool.

Himanshu - For this issue, we're sure that other Office apps are not affected - we did a very complete test pass.

Phawinpon.C (and anyone else who see's the error: "The expected version of the product was not found."  All indications are that this means you have a beta version of Office 2007 SP1 installed.  If you use Add/Remove Programs to uninstall Office 2007, and then reinstall Office 2007 (but not the SP1 beta), then the patch should apply correctly.  This is due to the way Office patching works - it only applys to versions of the product that are generally in-market for the public.

Korn1699 - We are not releasing a new converter at this time, but this patch can be applied to the converter if you have it installed.

Will there be notice given on this blog when this patch hits Windows Update?

Unless you have been on a deserted tropical island, you would have heard about the Excel 2007 bug whereby

Duh! That happens to be tha maximim value of integers for a 16-bit OS!

Ever try to see what the default value for the last cell in Excel is? I'll give you two guesses...

I have to chuckle every time I see that one dudes sig that has the faux dictionary entry for Windows:

win-does: A 32-bit extention and graphical interface for a 16-bit patch for an 8-bit OS from a 2 bit company that can't stand one bit of competion.

...or something along those lines, I'm quoting from memory!

Just goes to show how much effort they actually put into futhering their software. Just making the "pig" prettier!

Cheers,

Bryan

Apparently Microsoft Excel 2007 can't do it's times tables. Microsoft employee David Gainer, has posted on the Excel Blog that when computer users try to get Excel 2007 to multiply some numbers,...

I posted a detailed analysis based on disassembling Excel at

http://www.lomont.org/Math/Papers/2007/Excel2007/Excel2007Bug.pdf

I show why precisely the 12 values format incorrectly, what chnaged from earlier versions, and how the hotfix corrects the bug.

Chris Lomont

Chris,

The most comprehensive and well written article on the subject...I dont think any one in MS could have done a better job...

Sam

Will this be available through Windows Update?

After Excel bugs , where resolved , I started to pay attention of what this program provides me. I noticed

I tried to apply this patch and it said that "I have no affected products", but I do have Office 2007 SBE and my Excel 2007 does suffer from the calculation bug.

C'e' stato del trambusto nei giorni scorsi per un bug si excel 2007 dove in visualizzazione anziche'

To anyone else getting the "The installation of this package failed" -- it's not a beta version problem necessarily; you also need Windows Installer 3.1 v2 for the patch files to work. This is available as KB893803.

~Felix.

David,

Kindly patch up the copy of excel on your servers... when to "test drive" excel 2007 in the Web browser...the rendering bug still appears...

Sam

>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.

Dan and Dave, and Bill and every M.S. developer for that matter: please PLEASE study this carefully. That little post may well be the essential expression of what is wrong with Microsoft. If you do nothing more before Judgment Day, "get" what is wrong here. Please "get" its inexcusability.

Brace yourselves: no, the solution is NOT to instead say "Runtime error 1004, application defined or object defined error"

Hi David,

Below is a link highlighting something which I feel should be categorized as a "BUG". I am reporting here because I don't where I should have been reporting. Sorry for that.

http://www.asap-utilities.com/blog/

Problem with copying filtered data in Excel 2007 + workaround

It says "you cannot copy only the filtered data in Excel 2007. If you use the autofilter to make a selection and then you only want to copy the filtered rows, Excel 2007 copied everything, even the hidden rows. This is different from the way Excel 2000-2003 works". In that way Excel 2000-2003 is better than Excel 2007.

Regards

CA kanwaljit Singh Dhunna

India

See below

$145,510.22000000000000000000000000000000 +

$(72,140.74000000000000000000000000000000)+

$(32,041.10000000000000000000000000000000)+

$(30,658.61000000000000000000000000000000)+

$(8,848.40000000000000000000000000000000)+

$(800.22000000000000000000000000000000)+

$(521.48000000000000000000000000000000)+

$(499.67000000000000000000000000000000)=

$(0.00000000000289901436190121000000) should be exactly zero where do the extra numbers come from.  Excel does this on a host of other calculations as well.

Microsoft Excel Criticism Excel 2007 display error On September 22 September:September 22, 2007 2007:2007 it was reported<ref>