>Well, this is not our Scenario. ;)
>For Compatibility Issues we've to use the .net Winforms Control Version of the Control. So we put the .Net Control in an ActiveX Container, and this container is used in the VFP Form...
>Bud to easy test the Szenario and to eliminate one factor, we tried to use a simple winforms Textbox in an activeX container, and the same Behavior is there.
>I think this must be an Property anywhere. Bud witch?

Jörg,

The purpose of my message was to point out that regular integration of TX TextControl with VFP would not prevent the user to edit Cyrillic character data, and wouldn't even prevent VFP to process the data (problems would rise if there would be a need to support different character sets at the same time for the same text unit, but that does not seem to be the case).

I know that TX ActiveX and .NET are not the same, but I do not believe they would behave differently regarding this matter.

As Thomas suggested, most probably you should look into the other involved layers of the scenario, in particular, the ActiveX container you're using to wrap the controls.