Hi Ricardo,

Thanks for the reply. Sorry if I didn't make myself clear in my previous post. I tried what you suggested and it works, problem is that I need to store Japanese, Chinese, Korean and Roman Characters in the one table and still be using an Enlgish Version of Windows. With the W2K and VFP6.0 approach it works fine if you only want to use one language type ( please correct me if I'm wrong ). With Access 2000 I was able to store multiple languages in a single table and deploy this on Win 98 machines that had no Asian Language Support installed ( other than the MS Unicode Font ) and it worked perfectly. I was hoping the same would be possible in VFP6.0.

Thanks,
Gavin...

>Hi Gavin, we really need more details here on what went wrong with your DBCS application.
>
>I sent this to one of our internal VFP aliases and here's some of the feedback:
>
>"On W2K, make sure the default for the "Language Settings for the system" in Regional Options in Control Panel is set to Traditional Chinese, Simplify Chinese or Japanese depending upon the language you want. By changing just the Locale information in "Settings for the current user" will not have any effect. To type Chinese/Japanese, make sure to add the the IME in Input locales in Control Panel."
>
>
>"I tested VFP6 with the Win2K Localization set to Japanese and was able to get the Japanese DBCS characters to display in and be recognized by VFP w/o any problems. I had to Use a Font that has a Japanese script and make sure that the Font Script is set to Japanese. I also was able to enter DBCS chars using the Soft Keyboard in Win2K.
>
>"couldn't get the DBCS support to work" is a pretty wide term. Will need specfic examples of what does not work.
>
>
>- Ricardo