I have heard that Unicode is not supported. However, the problem I am having is that the run-time and development versions show different character sets (note the citation below). What causes this alternate character set (e.g. the U+2557 char)? Does that mean run-time supports it and development does not? Whether it is or it isn't is kind of mute. I would just like to know what is going on. Any clues?

>VFP doesn't support Unicode.
>
>>I am displaying a character using ? or @SAY (legacy stuff running under VFP6) with screen font set to "Courier New". On Win2k PC's the .EXE version executed with run-time DLLs shows a different character set than the exact same program run from command window.
>>
>>The character is CHR(187) - double arrow quote. When launching run-time EXE on Win2k it shows the graphic line symbol (U+2557 in character map).
>>
>>So, I wrote a little program to dump all ASCII chars from 33 to 255 and built a little EXE. Sure enough, the entire set shows the graphics symbols under run-time EXE. Then I tried different fonts and every one shows different character set under run-time execution.
>>
>>Is this a Win2k setting somewhere? Even if it is, why does it show differently in development version than in run-time? Anyone know?