Yes, Excel does with regards to ASCII code 32, but it doesn't with regards
to ASCII code 160. The SUBSTITUTE function is what did the trick to get
around the ASCII code of 160.

Give it a try yourself. Both ASCII codes are spaces, but they aren't the
same as far as converting text to numbers within Excel is concerned. When I
initially started to check it out, I thought it was the standard space
character, but then when I applied the CODE function to the last character
of the imported text, it returned the code of 160, not the expected code of
32.s

Now why the webmaster had used the ASCII code of 160 instead of the standard
ASCII code of 32, I have no idea. That's just how the information was
imported into my Excel file from the web page.

--
Ronald R. Dodge, Jr.
Production Statistician
Master MOUS 2000

"Harlan Grove" wrote in message
ups.com...
JE McGimpsey wrote...
...
For a formula:

=TRIM(SUBSTITUTE(A41,CHAR(160)," "))
...

The TRIM is unnecessary if the ultimate goal is numeric conversion.
Excel will ignore any number of leading and/or trailing ASCII spaces
[CHAR(32)] when such strings are used as arithmetic operands. E.g.,
=(REPT(" ",32)&"123"&REPT(" ",20))+1