Excel trucates contents of cell

[Guest]

First of all please forgive me if I have posted in the wrong section, or if
this question has been answered elsewhere, I'm a Newbie


I'm trying to enter the following text into a plain old cell in Excel:

MV[space]54[space]MYU

When I tab or enter, the content of the cell drops the "U". It keeps it if I
put the text in without the spaces, and then click the cell and re-add them
in the formula bar at the top.

My guess is that Excel is recognising the first 8 characters as something
else, which is why it's dropping the ninth, but even with the format of the
cell set to TEXT, this behaviour still occurs. (And yes, I've cheecked the
column widths, LOL.)

It occurs in Excel 2003 (fully patched) and 2000 SP1, which is why I think
I'm missing something rather than it necessarily being a bug. I bet it's
really obvious but I just can't see it.

 

[Tom Ogilvy]

In autocorrect, there is an entry to replace myu with my - excel considers
it a common mispelling, so it corrects it for you. If you enter myu alone
in a cell, you will get the same behavior.

 

[Guest]

Fantastic. Thanks for your help!

In autocorrect, there is an entry to replace myu with my - excel considers
it a common mispelling, so it corrects it for you. If you enter myu alone
in a cell, you will get the same behavior.

--
Regards,
Tom Ogilvy

First of all please forgive me if I have posted in the wrong section, or if
this question has been answered elsewhere, I'm a Newbie


I'm trying to enter the following text into a plain old cell in Excel:

MV[space]54[space]MYU

When I tab or enter, the content of the cell drops the "U". It keeps it if I
put the text in without the spaces, and then click the cell and re-add them
in the formula bar at the top.

My guess is that Excel is recognising the first 8 characters as something
else, which is why it's dropping the ninth, but even with the format of the
cell set to TEXT, this behaviour still occurs. (And yes, I've cheecked the
column widths, LOL.)

It occurs in Excel 2003 (fully patched) and 2000 SP1, which is why I think
I'm missing something rather than it necessarily being a bug. I bet it's
really obvious but I just can't see it.