>>
>>No, I don't think so either. I think it's the character mapping of the font being used. For example, if you use Arial, Tahoma, or MS Sans Serif, CHR(167) prints as §. However, if you use FoxFont, it doesn't.
>>
>
>By George, that does it *grin*. I hadn't tried FoxFont.
>
>Thanks!

Steve,

Something clicked in my head since I made my last post on this subject. VFP has two functions that may be of interest even though they're provided strictly for backward compatibility. They are OEMTOANSI() and ANSITOOEM(). What they do is convert between the two character sets. Try the following in the command window:

? OEMTOANSI(CHR(21))
? ASC(OEMTOANSI(CHR(21)))

The first will display the § character, the second will return 167.