Re: Difference between Client Access file transfer and FTP

John Cirocco wrote:
> 
> 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

John,

  Have you looked to see if your transfer is using an FDF on the PC to describe 
the data being transferred?  It may be that the data description there
does not match the file on the 400.

Terry Grider
+---
| 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
+---