|
Hello,
I am hoping someone here can help me. I have a process that is transfering
files from a /400 to an NT server via Client Access file transfer. The
transfer is kicked off via RobotClient. It has been in place a while and we
constantly have problems because RobotClient is 16bit and requires a router
session. So, to improve our process we decided to change the job to send the
file directly via FTP.
What we found out was the original file transfers were not sending the data
correctly. What was a 3 byte zoned numeric was actually transfered with CA as
a 4 byte field where the numeric fields were filled with BLANKS and not ZEROs.
When we transfer with FTP, the files as sent correctly. I know I need to
re-create my SQL Server imports for the "new" file layouts but I am extreamly
curious as to why CA pads my ASCII file with blanks and adds an extra position.
Any help and sedatives will be greatly appreciated...
John
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.