Dragan,

Thanks a lot for your Help. I will try tomorrow (if I'll have time) or on Wensday.

BTW, Andre Payette #029328 wrote me, that it's known bug.

See KB Q167675: BUG: Certain Non-US Characters Do Not Display Properly in VFP. http://support.microsoft.com/support/kb/articles/Q167/6/75.asp


>> I found HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\control\Nls\Codepage ACP.
>>Did you mean I have to change only this and live happy after all? Is it safe to change? I'm a little nervious... :)
>
>Well, you have to reboot after that, and if your fonts and .nls files don't support the codepage you selected, you may be unable to boot, or would boot into an unreadable desktop (because Windows would find the nearest suitable set of fonts if it thought the system fonts were wrong, and they'd be wrong if they wouldn't contain the designated codepage). If you're running Russian Windows, you should already have that set.

No, I'm running US Windows with Russian support.

>
>>part of the registry before changing anything. I've had problems on an NT
>>
>> How can I save it?
>
>Mark the part of the registry on the left pane that contains this key (i.e. HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\control\Nls) and choose File/Export from the menu. You get a .reg file, and a simple click on that will load its contents, replacing whatever you may have changed. You can run

Regedit yourfile.reg

from DOS prompt (unless you're stuck with NT) if boot fails.
>
>Last time I did this it worked after a couple of retries. I actually had support for all - 1250, 1251 and 1252 and ran regedit on each version of the .reg file from autoexec.bat (on a W95OSR2 machine), and depending on that, after booting I was able to run VFP on WestEuropean, CentralEuropean or Cyrillic fonts.
>
>You should also make sure that the codepage of your tables, screens, reports and classes matches the charset you are using - check the cpzero utility, it should be somewhere in your vfp\tools directory.
>