+1
The file transfer software can get real finicky.
Paul Nelson
Office 512-392-2577
Cell 708-670-6978
nelsonp@xxxxxxxxxxxxx
-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of rob@xxxxxxxxx
Sent: Thursday, November 03, 2011 3:12 PM
To: Midrange Systems Technical Discussion
Subject: RE: uploading dbase files using iSeries Access for windows
Not all of us are familiar with the term "dbase". dBase was a popular PC
based database program, apparently still in use. It's files are stored as
.dbf files on the PC's disk.
I think your idea of asking for a .csv file is a good approach. If the
trading partner is willing - dump the one conversion on them. Sending
files in proprietary formats is generally not kosher. csv, xml, ansi
x.12, edifact, etc are better alternatives.
You may wish to skip System i Access for windows file transfer though. For
example I would caution against using file transfer to transfer the csv
file to db2 on the i. Let's say they put a 18 char alpha into a field
that is only 15 on the i. I had this garbage all the time. If, instead,
you transfer the stream file to the i and then use a program to read the
stream file you can do better, granular editing on the file. Some
education on reading stream files and posting them to db2 can be achieved
at
http://www.scottklement.com/rpg/ifs.html
Rob Berendt
midrange.com
