|
I am using CA file transfer. If I tell it to use the fdf, it transfers for again each record in the 400 is layed out different depending on the lengths in the csv record. for example: csv record: rec1- "19960202","Preauthorized withdrawal","100.00" rec2- "19960202","Check#",1000.00" So when it transfers to the AS400 it basically leaves it like that on each line so I can not say Check description is in positions 13 thru 19 and amount is in positions 21 thru 30, because it's not on every field. If I say to transfer by file type and select CSV I get an invalid token on the transfer in the SQL statement, which I have no idea what to look for or fix there. >What are you using to upload the file? Depending on the file transfer >utility, you have several options. >Client Access and others will handle csv files. If you go to some trouble >in Excel you can convert the csv to prn(fixed length text) which ought to >work with just about anything. > >> >> HELP!!!!! >> Our bank gave us a new software program called KEYVIEW. We >> pick up our file >> from them with our check reconcilliation. The software gives >> us the ability >> to export the data out to either .csv or .bai format. I have >> typed a file >> with .xls extension to create an excel file also and it allows this. >> >> Now for the problem, when I transfer any of these files up to >> the AS400 the >> fields are not in the same positon. I transfer it up to a >> 300 char line >> file. Because the fields are not fixed length on the pc file >> they are just >> separated by a comma on the 400 file. I really do not want >> to get into >> having to read the 400 file char by char to determine the >> beginning and >> ending positon of each field. If I put the file into excel >> first, it looks >> great on excel, each field is separate. If I save it as .xls and do a >> transfer it transfer 1 record and it is encrypted! The file >> really has >> about 900 records. Is there something I can do, or does >> anyone else use >> keyview and how did they handle this? >> >> >> Thank you in advance, Angie >> >> +--- >> | 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.