>If I'm not mistaken, VFP doesn't use Unicode for I/O, so it's important to have its operating environment set up for the particular language (i.e. the code page that it's running under should match the language being used) -- i.e. double-byte characters generally only work if you're in a mode that utilizes it. As long as your development environment and the runtime environment match, you generally don't have to do anything special. Peculiarities tend to crop up if the development environment and runtime don't match -- I'd learned a long time ago to avoid certain characters in string literals -- typically strings that end with a character that's in the "high-ASCII" range (ones where ASC() would return values above 127), as typically such characters are used as "shift-In"/"Shift-Out" modeswitch or lead-in bytes for double-byte characters in Asian language. If you wrote program in English, and run in English mode, the program works OK, but you start getting syntax errors, unterminated string literal errors, and several other errors. If you switch development environment to the target Asian language, then open the PRG, FRX, or SCX files, those errors will be flagged when you try saving. After adding the fixes and recompiling (in the target language) usually gets rid of the problems -- then a different one surfaces. When run in English, the program starts displaying extra "gibberish" characters.

Actually the report has two languages which are indonesian language and mandarin language, so I tried to setup up the operating environment with chinese and english language but it didn't work out. I've tried the report listener class in VFP but I stil can't find the way. Do you have any idea, Naoto ?