Newsgroups: comp.databases.sybase,fj.comp.misc,comp.software.international
Path: galaxy.trc.rwcp.or.jp!jaist-news!cs.titech!wnoc-tyo-news!sh.wide!news.Hawaii.Edu!ames!elroy.jpl.nasa.gov!swrinde!ihnp4.ucsd.edu!pacbell.com!amdahl!netcomsv!netcom.com!fletch
From: fletch@netcom.com (Morgan Fletcher)
Subject: bcp-ing in shift-JIS or JIS CSV (Sybase)
Message-ID: <fletchCoxq1L.Ey9@netcom.com>
Organization: NETCOM On-line Communication Services (408 241-9760 guest)
X-Newsreader: TIN [version 1.2 PL1]
Date: Wed, 27 Apr 1994 20:24:57 GMT
Lines: 24
Xref: galaxy.trc.rwcp.or.jp fj.comp.misc:2344
X-originally-archived-at: http://galaxy.rwcp.or.jp/text/cgi-bin/newsarticle2?ng=fj.comp.misc&nb=2344&hd=a
X-reformat-date: Mon, 18 Oct 2004 15:18:22 +0900
X-reformat-comment: Tabs were expanded into 4 column tabstops by the Galaxy's archiver. See http://katsu.watanabe.name/ancientfj/galaxy-format.html for more info.

I must first say that I am not an MIS person, but I do have a good bit of
experience with our company's Sybase database software.

I'm in the US, and I'm working with a Japanese partner, and they'll be 
sending me data from Paradox for Windows-J (the Japanese version of Windows 
and Paradox). The data will be a mixture of Roman and Kanji text. I expect 
that the best solution will be to have them export shift-JIS or JIS CSV 
data, as I understand that Sybase's bcp program can import data that is 
in other text formats aside from ascii.

We don't want the Kanji data (confined to one field) to import, so we'll
just exclude that field in the .fmt file. We are running SQL Server 4.9.2 
on SunOS 4.1.3 on a Sparcserver Model 30.

MY QUESTION: What is involved in bcp-ing in CSV data that is in shift-JIS
or JIS text format into a US implementation of Sybase? Also, given a 
Japanese db product (Paradox), is there another, better metafile format 
than CSV for importing into US Sybase?

Thank you for your attention and time,

Morgan Fletcher


