Greetings!

I have an application that can happily store and retrieve Japanese
characters into a stand-alone FoxPro database. Now I need to write them
into nvarchar fields in SQL Server tables. SQL Server is expecting them in
Unicode.

I have an edit box into which I can enter Japanese characters through an
input method editor. I haven't been able to figure out how to massage those
characters to get them into Unicode and then into the SQL Server table.
What hoops do I have to jump through?

Thanks!

RobR

RE: Store Japanese characters from FoxPro into SQL Server? by Leemi

Leemi
Wed Aug 04 14:45:41 CDT 2004

Hi Rob:

I have not tested this, but I will give it a shot.

Look at the Strconv() function in VFP to convert the string to Unicode. On
the SQL Server side, I think you need to set the code page of the SQL
Server database to Japanese. However, I could be wrong on this point.

I hope this helps.

This posting is provided "AS IS" with no warranties, and confers no rights.

Sincerely,
Microsoft FoxPro Technical Support
Lee Mitchell

*-- VFP9 Public Beta Now Available!! --*
Download the VFP9 beta here: http://msdn.microsoft.com/vfoxpro/

*-- VFP8 HAS ARRIVED!! --*
Read about all the new features of VFP8 here:
http://www.universalthread.com/VisualFoxPro/News/VFP8Release.asp
Purchase VFP8 here:
http://shop.microsoft.com/Referral/Productinfo.asp?siteID=11518

Keep an eye on the product lifecycle for Visual FoxPro here:
http://support.microsoft.com/default.aspx?id=fh;[ln];lifeprodv
- VFP5 Mainstream Support retired June 30th, 2003
- VFP6 Mainstream Support retired Sept. 30th, 2003



>Greetings!

>I have an application that can happily store and retrieve >Japanese
>characters into a stand-alone FoxPro database. Now I need >to write them
>into nvarchar fields in SQL Server tables. SQL Server is >expecting them
in
>Unicode.

>I have an edit box into which I can enter Japanese >characters through an
>input method editor. I haven't been able to figure out >how to massage
those
>characters to get them into Unicode and then into the SQL >Server table.
>What hoops do I have to jump through?

>Thanks!>