Hi Rick!

>Can you set the character set for editing in the control? It sounds like the control is set for a western Ansi character code and you probably want a Unicode character code instead.

Ok, bud where do i have to set the character set? I can't find a Property or rather if I set the Font.Charset property, it has no impact.

>But... if you do that the problem becomes how to get that data into FoxPro - unless you're running in a compatible character code in FoxPro the text will be all gibberish when you go from extended Unicode to Ansi. Unless you use the Russian code page explicitly.

We store the Data from this Control in HTML Format so there's no Problem with storing the Unicode data ;)
AND, I have to say: It works fine with Chinese Chars, bud the Input is different, if I Type the Chars appear in a other Window to select the right Chines-Char, and if i Select it works... (see Pic Chinese vs Pic russian)

>FoxPro can't handle multiple code pages in strings at the same time so the only way to get the data in and out is to have the code page set correctly each time you use the data.
>
>It's a nasty problem and one of the reasons that VFP is problematic for multi-lingual applications that span different character sets/code pages.

We are aware of this Problem. We build a technique in our VFP Program so the User can select the Fontcharset of each Record, and than we store the Data to SQL Server, according to your great Artikel "Using Unicode in Visual FoxPro Web and Desktop Applications".
This all work well, despite the stupid .NET Control...

>
>+++ Rick ---