Hi,

This problem has been haunting me for more than a year and I am dying for a ghost buster...

In my entry form when user try to input Chinese characters with WinXP's Chinese (Simplified) - Microsoft Pinyin IME 3.0:

The input will fail, 9 out of 10 times.
The IME does pop up to let user input Chinese characters, but it pops up abnormally - obviously something is wrong, because it will place its input cursor outside the field being edited (or even outside the entry form itself) and when that happen, Chinese character won't be placed in the field.
No matter how many times the IME is switched between English and Chinese input mode, the problem remains.

-------------------
The Alt+TAB trick:
-------------------
After about 12 months intensive research, I finally discover a trick - when the IME behaves abnormally, just Alt+Tab to another program then Alt+Tab back to the VFP entry form, that is it, the IME will start to work correctly. Btw, if there is no other program to Alt+Tab to, just press the WinXP's Start button (which brings up the start menu) and then switch back to the entry form, that will also do the same correction.

But I find it ashame if I were to tell my user that my "Alt+Tab trick" is the only way to make inputing Chinese possible in my application.

The below are some observations:
1. After my entry form get started, when user try to input Chinese character through the IME for the very first time, the IME normally will behave incorrectly.
2. After user does the Alt+Tab trick as described (to make the IME work correctly), thereafter, every where in the entry form, the IME will always work correctly as long as the form is not closed.
3. Once the form is closed and restarted, well... again Alt+tab trick is required to correct the IME.
4. My test machine has English WinXP+Sp2 installed, non-unicode language is set to Chinese PRC and the "Extend support of advanced text services to all programs" is checked.

I strongly suspect it is a bug of "WinXP's Chinese (Simplified) - Microsoft Pinyin IME 3.0"...
Instead of simply making MS the one to be blamed, I hope there is a real solution (not by using my Alt+Tab trick)...

If anyone have a solution or just anything better than the temporary solution I have found, please help!