Mornin' George,

>
>Steve,
>
>Something clicked in my head


Did it hurt? <g>

>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.
>

That is interesting. So, I wanted to see how it would work with another problematic EDI characters One possible EDI element seperator is chr(127), which looks like homeplate (yes, baseball) in ASCII. It displays properly in FoxFont, but the OEMTOANSI() still renders it incorrectly (I'm using that term loosely) in other fonts.

According to HackFox, OEMTOANSI() works for characters 15, 20, 21 and those above 128.

Thanks for the additional info...