Filepro-list Digest, Vol 115, Issue 14

[Boaz Bezborodko]

Mirrotek International, LLC
90 Dayton Avenue
Building 1-F
Passaic, NJ  07055

Tel:  973-472-1400 x.112
Fax:  973-472-5170

On 8/19/2013 8:48 AM, filepro-list-request at lists.celestial.com wrote:
> Send Filepro-list mailing list submissions to
> 	filepro-list at lists.celestial.com
>
> To subscribe or unsubscribe via the World Wide Web, visit
> 	http://mailman.celestial.com/mailman/listinfo/filepro-list
> or, via email, send a message with subject or body 'help' to
> 	filepro-list-request at lists.celestial.com
>
> You can reach the person managing the list at
> 	filepro-list-owner at lists.celestial.com
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Filepro-list digest..."
>
>
> Today's Topics:
>
>     1. Re: Re Export (Kenneth Brody)
>     2. RE: Re Export (Richard Kreiss)
>     3. Strange behavior with IMPORT (Boaz Bezborodko)
>     4. Re: Strange behavior with IMPORT (Jean-Pierre A. Radley)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Sun, 18 Aug 2013 12:14:50 -0400
> From: Kenneth Brody <kenbrody at spamcop.net>
> Subject: Re: Re Export
> To: Richard Kreiss <rkreiss at gccconsulting.net>
> Cc: "filepro-list at lists.celestial.com"
> 	<filepro-list at lists.celestial.com>
> Message-ID: <5210F2FA.5040701 at spamcop.net>
> Content-Type: text/plain; charset=ISO-8859-1; format=flowed
>
> On 8/17/2013 2:49 PM, Richard Kreiss wrote:
> [...]
>> 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.
> The *what* are spaces?
>
>> My problem is when I look at the file created, most of the exported
>> records are on 2 lines not one.
> [...]
>
> Could it be as simple as the program you are using to look at the file is
> wrapping the long lines?  (Or, are you exporting fields that contain newlines?)
>
> How, exactly, are you looking at the exported file?  And how, exactly, is
> the record broken into two lines?
>
I tried using "echo. >> {filename}", but that added a CR-LF and it still 
gave me the same problem.  I'm using Filepro on Windows XP machines.

But why does it give a 'not {file}' equals 'true' with the fields for 
the file have valid data?

Boaz