Re: Japanese to Unicode characters
From: Steve Kass (skass_at_drew.edu)
Date: 12/06/04
- Next message: David Gugick: "Re: Deadlock handling"
- Previous message: Alejandro Mesa: "RE: Programmatically Dropping databases"
- In reply to: Vital: "Re: Japanese to Unicode characters"
- Messages sorted by: [ date ] [ thread ]
Date: Mon, 06 Dec 2004 14:25:24 -0500
Vital,
I agree with what Bart said: it sounds like your source data is not
stored as Unicode, so it depends on the code page setting for correct
interpretation. His suggestion to export the data to a flat file, then
import it into nvarchar() columns with the appropriate code page
specification, sounds right to me. The tools you're using should
all work with nvarchar source columns.
The goal is to export the data to a flat file that you
can read in Japanese on the Windows 2000 machine.
If you cannot get that far, it's not a SQL Server problem.
If you do get that far, but something fails later, please
be specific about what you did and why you think you
didn't succeed. You have at least three machines here
(VAX, Japanese Win98, Win2000 Server), so be
specific about what files are where and what applications
you are using on what machines to look at them.
SK
Vital wrote:
>Steve,
>
>In fact it is not so easy...
>
>I have 2 applications:
>- the old one is working with OpenVMS on a VAX machine and uses an
>Oracle-Rdb database; a VB application running on a Window98 Japanese PC
>read/updates the database through an Oracle ODBC driver for Rdb; Rdb doen't
>store the japanese strings as Unicode. To work with these strings it was
>necessary to set the VB textbox Font to MS Mincho (with the Japanese
>script).
>
>- the new one is working on a Win2000 server and uses a SQL2000 dB. A VB
>application running on the same machine read/updates the database. To work
>with the Japanese strings (declared as NVarChar in SQLserver) we uses an
>UniToolBox component for VB which handle the Unicode strings.
>
>Now I want to migrate the data from the Rdb to SQLserver dB and store the
>Rdb Japanese strings into Unicode SQLserver fields; but I cannot store them
>as they are because they will not be understandable for the other Unicode
>compatible tools (UniToolBox, CrytalReport, etc.) !
>
>Any ideas?
>
>"Steve Kass" <skass@drew.edu> wrote in message
>news:41B08DB8.4050805@drew.edu...
>
>
>>Vital,
>>
>> There's nothing special about storing unicode in a SQL Server table if
>>you declare your column as nvarchar(-put suitable length from 1 to 4000
>>here-). Unicode strings specified as literals must include the N
>>indicator, as in N'unicode string here'. Is your question just "how do
>>I store anything in a SQL Server database?" or are you having trouble
>>with this particular kind of data?
>>
>>Steve Kass
>>Drew University
>>
>>Vital wrote:
>>
>>
>>
>>>I have to migrate a Japanese application from Oracle-Rdb to SQL2000
>>>database. I use an Oracle driver to get the japanese strings. To be sure
>>>
>>>
>I
>
>
>>>read correctly the values from the source database, I display the strings
>>>
>>>
>in
>
>
>>>a VB textbox with MS Mincho (Japanese script) font and this is fine.
>>>
>>>Now I want to store these strings into Unicode fields (nVarChar) in a
>>>SQL2000 database... how?
>>>
>>>
>>>
>>>
>>>
>>>
>
>
>
>
- Next message: David Gugick: "Re: Deadlock handling"
- Previous message: Alejandro Mesa: "RE: Programmatically Dropping databases"
- In reply to: Vital: "Re: Japanese to Unicode characters"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
