>FontCharSet is only relevant to the display font characater set, not to how the data is stored in tables. Two VERY different things, and unfortunately, two things that do not work well together in VFP if you want a language other than the Windows localized language.
>
>IOW if I am running, for example, Hebrew Windows, I can set the codepage and store Hebrew data in a .dbf. I can also set the FontCharset for display.
>
>But if I am running US Windows, I may be able to display Hebrew charactes, but they cannot be stored as only codepages native to the Windows version are supported. Check out Rick Strahl's article.

It's been a while since I last used dbfs for anything but pet projects (and in those I have everything in cp 1250, CE windows, as is my machine, so no problem there). On the side I'm helping a friend who has to mix cyrillic and latin scripts in some places, and found that two things help a lot (but don't solve all the problems):

- set the codepage for non-unicode programs to what you need - 1251 for cyrillic, 1250 for CE etc; that solves the display (except form captions and possibly menus)

- make your character fields binary, i.e. nocptrans - then you don't get anything converted, no question marks etc, and Fox doesn't care which codepage is it meant to be.