Re Export

[Scott Nelson]

I have done this for several customers to export their check lists to 
the bank.  Your export needs to be one field that you construct from 
fixed length real or dummy fields all concatenated together.  You may 
need some zero padded left justified fields for amounts for example, and 
that would be one of the dummies.   You can then alternate what is 
populated in the dummy that is the saved field, based on the need for 
header, detail and footer records, or in your case, 2 lines for each 
data segment.

I can send you some sample code if you need.

Scott


On 8/17/2013 1:49 PM, Richard Kreiss wrote:
> One of my client's needs to have me create a Nacha format file for handling ACH payments.
>
> Each record is 94 bytes long and is made up of 13 fixed sized elements.  Similar to IMB RPG programming language.
>
> I have created a long variable foobar(94,*) to hold each element also long variables of the proper size for that element.  IN some cases numerical values are zero filled and in others either left or right justified with blanks to fill the element or field. Also, in some of the alphanumeric fields which call for a name the  are spaces.
>
> My problem is when I look at the file created, most of the exported records are on 2 lines not one.
>
> Windows server 2008, Windows 7 on the desktop, filePro 5.6.10
>
> My command line is:
>   Export ascii nacha = (filename) r=\n
>
> How do I tell filePro when using export to ignore spaces and treat the whole field as one record?  Or, do I need to use filePro I/O writeline() to accomplish this?
>
>
> Richard Kreiss
> GCC Consulting
>
> Office: 410-653-2813
>
>
> _______________________________________________
> Filepro-list mailing list
> Filepro-list at lists.celestial.com
> Subscribe/Unsubscribe/Subscription Changes
> http://mailman.celestial.com/mailman/listinfo/filepro-list
>
>