>>This was fine last night, now when I run the app (old @ Say stuff) the characters are looking pretty messed-up. For example, rather than displaying a block (ASCII 219), it is displaying the Uppercase "U" with the little dot over it. Other characters in the extended set are doing the same thing. This really isn't Foxpro, because what changed happened when nothing in Foxpro was changed. It must be a Windows/XP thing, but I figure that since the problem is showing itself in Foxpro, I would ask the question here. Please help, my screen look like crap. Ok, worse crap... Thanks!
>>
>>Update1: Ok, it's clearer, but stranger... If I have VFP open, then everything displays correctly when running the EXE, but if I close Foxpro, then I'm back to having crap characters. Foxpro is setting something, but how do I handle this correctly if the client wont' have Fox development running?
>>
>>Update2: I think it has to do with having FoxFont fonts available. Does anyone know where they need to reside in relation to the EXE? I put them into the same directory, but they did not catch. Do I need to rebuild the EXE with the fonts in the directory?
>
>Hi Renoir,
>
>This looks like a problem with the codepage selection. Since the title says VFP 8, I assume you are using VFP and not old FoxPro.
>
>In that case, I would say the problem lies in the font selected. For instance, perhaps you are using FoxFont on your machine, but this font isn't available on the client machine. FoxFont basically uses the old DOS font, while most other fonts (like Arial, or Times New Roman) use a Windows font. If a font is not found, some standard font will most likely be substituted.
>
>HTH,
>
>Hilmar.

That was exactly it. Somehow - and I have no idea how - the FoxFont and FoxPrint fonts got removed from the Windows/Fonts directory on my PC. I had a Language Bar pop on me when I booted up and I just closed it, so I'm not sure what was going on. Thanks!