|
This is exactly true, the easiest way to create an FDF file is to download a file that is setup with the same fields and all and save the FDF file it creates, then use that FDF to upload the file. If you have Client Access Express, it includes a Wizard that will write one for you on the fly... pretty neat. Eric Sundell AS400/PC Specialist The wages of sin are eternal damnation. The hours are pretty good though... ____________________Reply Separator____________________ Subject: Re: Client Access Transfer Extras Author: "Carl Galgano" [SMTP:cgalgano@ediconsulting.com] Date: 11/16/99 11:22 AM I haven't used CA is forever, so this may be a shot in the dark, however I do recall eons ago that when you uploaded a file you chose between a data or source file. For a datafile you had to have a .FDF (file description) file on the PC to tell the AS400 how the fields are on the AS400. If you uploaded as source, it did not have this requirement, however it added the bytes to the end of the file, because this is where the last update date and time stamp is kept in a SRC file. Hope I am lucky! CJG Carl Galgano EDI Consulting Services, Inc. 540 Powder Springs Street Suite C19 Marietta, GA 30064 770-422-2995 mailto: cgalgano@ediconsulting.com http://www.ediconsulting.com EDI, Communications and AS400 Technical Consulting -----Original Message----- From: Jeff Burcher <jburcher@cbcolcntr.com> To: MIDRANGE-L@midrange.com <MIDRANGE-L@midrange.com> Date: Tuesday, November 16, 1999 2:06 PM Subject: Client Access Transfer Extras >Anyone, > >When I transfer from PC to AS/400 via Client Access it adds 12 characters on >to the beginning of each record. Does anyone know what these are for other >than relative record number? > >When I transfer from AS/400 to PC via Client Access it adds a space to the >beginning of each numerical field. (I assume this is for the sign.) > > >How do I tell Client Access not to do these things? > >or > >How do I tell the AS/400 to mimic these Client Access add-ons via an FTP >transfer. (I assume there is a corresponding CCSID #.) > > > >Thanks, > >Jeff Burcher >AS/400 Programmer >GMA/CBCC >(336) 378-6300 x3207 >fax: (336) 378-6266 >jburcher@cbcolcntr.com >+--- >| 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 >+--- +--- | 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 +--- +--- | 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-2024 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.