Excel 2003 Incorrect Result for Division

[BlueHolly]

I am having a problem with a basic division calculation and am worried that I can't trust any Excel 2003 division calculations as a result.

I discovered this problem when I typed =6/35 into an cell in Excel 2003. Excel proceeds to change it to =6/53 and gives me the result of that calculation instead of the original one. It doesn't matter if the cell is formatted as General, Numerical, or Fraction. This doesn't happen when I use an old version of Excel 97. My processor is an Intel 3.0 Gz chip.

Anyone have a solution to this?

 

[Ron Coderre]

I can't duplicate your experience.
Does it only happen in one workbook or every workbook?

 

[BlueHolly]

It happens in new workbooks as well. The 3 and 5 get transposed prior to the calc being made.

 

[BlueHolly]

The only reference I can find relating to this problem is on the web is at the following site:

https://ask.qut.edu.au/app/answers/...lay-incorrect-results-in-microsoft-excel-2003.

However, this site implies that a Floating Point Unit (FPU) patch could be downloaded but I have not been able to find such a patch. Furthermore, it states that the FPU patch should be standard with Excel 2000 and later making my problem in Excel 2003 non-existent - obviously not the case!

 

[Derek Brown]

Have a look at the auto-correction options set for Excel.
As a test I was able to add such a correction and get it to make that change when I pressed Enter.

 

[Joe4]

Have a look at the auto-correction options set for Excel.
As a test I was able to add such a correction and get it to make that change when I pressed Enter.

I think Derek is probably spot on here. There is nothing wrong with Excel. It sounds like you have Auto Correct set to automatically replace 35 with 53. Just delete that Auto Correct record and you should be OK.

 

[BlueHolly]

Thanks so much guys!!! You were right. There was an entry in my Autocorrections that changed 35 to 53! I have no idea how it got there - maybe the kids. The solution was so obvious and I'm mad at myself for not having thought of it!

Issue resolved!!!!