>>>I guess it's something in the fonts on the NT, and the way VFP is using them. Office apps using the same fonts have no problem - the proper diacriticals show up. Does anyone know of a good old Indian trick for this?
>>
>>Too easy for an old champ like you, but since it seems specific to VFP, didn't you forget the FOXPRO.INT file?
>
>That's what I get for trusting the setup wizard (banging head against a wall)... Of course - and the W98 stations have VFP installed, and can find it. Great - I'll check it first thing in the morning.
>
>I expected they used wiser guys to play wizards... I mean, the tables use a local collating sequence on some tags, the indexing routine mentions collating sequence, almost every file with a codepage is marked 1250, and one'd expect that the setup wizard would be smart enough to include foxpro.int.
>
>Thanks... even if it gave me a momentary headache :)

Addition: the Foxpro.int file was missing - so I put it there, and now the localized index tags work properly, but the .exe still displays the characters as if the app was done in codepage 1252. I thought the codepage= line in config.fpw decided on the codepage VFP will use, but it goes only as far as to determine the codepage used as compiler's default codepage, and to mark new tables/forms/classlibs and other .dbf type files. It does not use this for font display - it probably uses the HKEY_LOCAL_MACHINE\System\CurrentControlSet\control\Nls\Codepage\ACP key. On the W9x machines where it works, it displays 1250-specific chars properly, and they have the value of 1250 in this key.

On my home machine I've tried to change this registry value to 1251 (cyrillic) and the same apps started displaying cyrillic (though some other things didn't work if I didn't have all the necessary .nls files installed in \windows\system), so it must be this key, though I've never found anything in docs about this.

The trouble with NT is that it never gave us a chance to choose the default system codepage, and searching through the system help and some NT bible on the codepage issue led me nowhere - it's even more cryptic and misleading than Office help. I really don't dare messing with NT registry - it's the server for the whole company, and the app is a wee phonebook and workorder log, installed there for the convenience of our secretary, so the app itself is not so important.

Still, I feel I'll have more of this problem as more NT machines will come my way: how do you get VFP apps to display localized character sets on a NT (SBS in my case) machine?