Anything's possible with external resources. (And no, I know nothing of character sets either.)

Dan


>Hi Dan,
>
>thanks for that. I'll try it out.
>
>Could the problem also be something to do with character sets? (Not that I know anything about character sets.)
>
>>Apparently there's such a thing as a "partial install" for fonts. I don't know specifics, but it's definitely possible to have fonts that some applications can see and others can't.
>>
>>Here's how to INSTALL a font (if you have the TTF) from VFP:
>>
>>http://support.microsoft.com/default.aspx?scid=kb;EN-US;186722
>>
>>Dan
>>
>>
>>>Hi Dan,
>>>
>>>the weird thing is the users say that Arial is installed! I think I have a Korean installation from some time ago that I'll look into installing and see if I can duplicate the problem.
>>>
>>>Thanks for the advice of using AFONT().
>>>
>>>>>Hi,
>>>>>
>>>>>We have an application that is distributed in many countries around the world. It has recently come to light that our forms that use Arial, 9pt for the labels display as if the font is Courier, but only at the Korean installations. Of course this means that some of the labels are illegible. Every where else is fine. Has anyone ever come across this before?
>>>>>
>>>>>Frank
>>>>
>>>>Many years ago, some installations of NT4 defaulted to not having Arial installed. In that case, though, VFP substituted Wingdings. (No I'm not making this up!)
>>>>
>>>>Ever since, I've used AFONT() in startup code to make sure any fonts I need are installed.
>>>>
>>>>Dan