> I am trying to get a DBF to display using a different code page. No matter > what I try, I can't get the text to display any differently in a grid or > browse. I think M$ screwed it up a little - for instance, it shows properly only the codepage installed on your machine. I need two of them - one Central European (1250) and one cyrilic (1251); my w95 is installed with 1250 with cyrilic support. OK, I can see all the ¹ðèæ¾ characters I need in CE, but for the hell of it can't force VFP to show cyrillic, except maybe on machines where w95 is installed with 1251 code page. For the same reasons, it won't allow me to switch to the third keyboard layout, and in some cases I need the fourth (yugoslav latin, ASCII, cyrillic, hungarian); well, most of the software behaves the same way, allowing for only two keyboards. The only exception to it (so far) is Office 97, and that also not everywhere. For instance, I can switch layouts as I like in Word or Excel, even have cyrilic titles on toolbars >), but can't persuade Outlook to have it in a folder name. This may get into a wishlist for some further edition of VFP (and other software as well), to conform to switchable keyboards, and using Unicode. Besides, how's VFP with unicode? Not compliant, I guess? It's a pity if it's so, because I'm having to invent something else for multilingual apps - in DOS, I used an environment variable, and had constructed program headings like this: #define lang_used=GetEnv("lang") #if lang="mag" c_msg="Szia" #elif lang="eng" c_msg="Hello" #elif lang="ser" c_msg="Zdravo" #elif lang="scy" c_msg="... " (here goes the cyrillic message, but Netscape...) #endif Now I simply can't type in the proper letters for another script, and can't just recompile using a different Set lang=xxx - I have to go to another machine where w95 is set in corresponding codepage. A solution may be to have registry saved according to another install, but... the solution is not that elegant, as just setting another value and recompiling. Any ideas?