On Jul 10, 12:48 pm, Eric wrote:
Somebody somehow managed to
get the 3.67 value into a cell (entering into another cell, copying and
pasting?), the cell displays as 3.7, but it calculates on the 3.67.

What revision of Excel are you using?

Based on my experiments with Excel 2003, I would guess that something
is wrong with your understanding or explanation of the situation.

I am looking at the internal binary representation.

When I enable Precision As Displayed, format a cell as Number with 1
DP and enter 3.67, the value stored and displayed as 3.7 has exactly
the same binary representation as when I enter 3.7 into another
similarly formatted cell.

When I format a cell as General and enter 3.67 (Jim's speculation), it
has a different binary representation, as expected. But after that,
if I format the cell as Number with 1 DP (what you claim to see post
facto), the value is displayed as 3.7 (as expected), and its binary
representation is the same as the 2 cells in the previous paragraph.

In summary, when Precision As Displayed is set, I have not found a way
for a cell formatted as Number with 1 DP and displaying a value of 3.7
to have a binary representation that differs from the literal constant
3.7.


----- original posting -----

On Jul 10, 12:48*pm, Eric wrote:
I have a worksheet I distribute to others to complete and return. I need data
entered to no more than one decimal place. So I have formatted the numbers to
one decimal place and enacted "precision as displayed." Once PAD is enacted,
if you enter 3.67 in a cell, both the display and the underlying value become
3.7.

At least this is the way it's supposed to work. Somebody somehow managed to
get the 3.67 value into a cell (entering into another cell, copying and
pasting?), the cell displays as 3.7, but it calculates on the 3.67.

I can sort of understand how the underlying value might show as 3.67, but I
definitely can't understand why PAD isn't overriding the calculation since
it's displayed as 3.7.

Is there an additional safeguard I could deploy, or is this just one way
that Excel isn't perfect? TIA.