>Hi
>I have the font Fixedsys.
>I don't see these two other fonts (FoxFont&Foxpro Windows Font), but I don't see these two fonts also in my old computer, that VFP work well.
>>>Hi
>>>I installed VFP (VFP9, SP2, HOTFIX3) on a new computer.
>>>
>>>Unfortunately, in most places, the font was unrecognized.
>>>I fixed big part of the cases, on Tools>Options>IDE , but there are still places that Vfp use with unfamiliar fonts, and I have not found a way to fix it.
>>>
>>>Attached is an example (places with unknown fonts, marked in yellow).
>>>
>>>Some cases I have the problem also in runtime (such as Inputbox typing), and some cases only on design mode (such as Message Box content).
>>>
>>>Thanks in advance
>>
>>I'm wondering if the missing font(s) in question might be one of the following:
>>Fixedsys
>>FoxFont
>>Foxpro Windows Font
>>
>>if I'm not mistaken these are "legacy" bitmap fonts. The metrics for bitmap fonts tend to get wonky if display isn't set the expected 96dpi - so perhaps in your configuration they've been disabled? If I'm not mistaken, Windows should automagically select a "similar" font if a program tries to use a font that is missing (as for which font gets selected, sometimes it's a hit-or-miss -- I'd seen the occasions where the "similar" font ended up being something like Wingdings or Webdings which results grawlix).
>>
>>One simple way to check to see if they're available is use Notepad and look under Format / Font and see if they're listed. (or if you want to do this within VFP, open up text editor with MODIFY COMMAND, then select Edit / Properties from menu, then click on the Font selection button, then scroll through the selections. You can type some text into the text editor and see how the font selection affects the display of that text).

Foxfont.fon should be found in the folder where Visual Foxpro 9 is installed.
(e.g. in "c:\Program Files (x86)\Microsoft Visual FoxPro 9" )

As stated by others, perhaps there might be regional settings that might affect this.

in Windows:
Settings --> Time & Language --> Language (on left-hand-side) --> Administrative language settings (on right-hand-side) --> Language for non-Unicode programs
(you'll probably need to have this set to "Engish (United States)" for Visual FoxPro to work properly)


speaking of language settings... I've noticed that if your Windows system set for East Asian languages such as Chinese, Japanese or Korean there may be certain "quirks" that you'll hve to be careful about. One of these has to do with string literals -- in particular avoid using ASCII codes in the 128~255 range within string literals. If you need them, build the string with CHR() function for any characters in that range. This is connected to the double-byte character systems used in those languages as "lead-in", "shift-in" "shift-out" and data character. What happens is that if such characters appear at the end of a string literal, such a character could be interpreted as a "lead-in" code for a double-byte character sequence -- thus "eating" the closing quote of the string literal. This results in an unterminated string literal, which could then trigger syntax error. Had this occur on a few occasions at customer site when language setting was set to any of the previously-mentioned East Asian languages.