Export ASCII -x

scooter6 at gmail.com scooter6 at gmail.com
Fri Nov 19 09:07:11 PST 2010


  Nancy,

  I have done both - but I do typically use the export ascii f=, r=\n type
export/import - have only done a few -x ones but
  have always used the r=\n, probably because I just assumed you had to and
never really read all the manual details on the
  -x option haha

  Glad it seems you have it working now though

  Scott

On Fri, Nov 19, 2010 at 9:23 AM, Nancy Palmquist <nlp at vss3.com> wrote:

> Scott,
>
> Do you usually do a "Export ASCII file -x" or the more standard "Export
> ACII file r=\n f=," version?
>
> It was the -x version that was supposed to provide the New Line and does
> not have any field delimiter.  That is what it seemed to do but not when I
> did not send at least one CR or LF.  When my data just was text it provided
> no CR/LF ending.  That was my complaint.
>
> Nancy
>
> On 11/18/2010 4:21 PM, scooter6 at gmail.com wrote:
>
>  FWIW, I have always used  r=\n on ALL my imports and exports and have
> never had any issues like you describe
>   So my assumption would be it's always required?!?!  (but, I don't like to
> assume haha)
>
>  Scott
>
>
>
> On Thu, Nov 18, 2010 at 4:17 PM, Jeff Harrison <jeffaharrison at yahoo.com>wrote:
>
>> ----- Original Message ----
>>
>> > From: Nancy Palmquist <nlp at vss3.com>
>> > To: filePro Mailing List <filepro-list at lists.celestial.com>
>> > Sent: Thu, November 18, 2010 2:04:14 PM
>> > Subject: Export ASCII -x
>> >
>> [snip]
>>
>> > Well I finally found what it needed.  So I guess this  turned out to be
>> a
>> > cautionary tale not a request for help after  all.
>> >
>> > 330  -------   -   -   -   -   -    -   -   -   -   -
>> > wrtxml ? If:
>> >          Then: export ascii myxml=(expname{"") -x r=\n
>> > 331  -------    -   -   -   -   -   -   -   -   -    -
>> >         ? If:
>> >         Then:  myxml(1)=myline{chr("10") ;write myxml
>> > 332  -------   -    -   -   -   -   -   -   -   -    -
>> >
>> > This caused my file to end up with CR/LF (0d 0a) just what was
>> > required.  What weird logic is causing this but here it is if anyone
>> > else is looking for a solution.
>> >
>> > Nancy
>>
>> Nancy, you still needed the chr("10") even after you added the r=\n ?  I
>> am not
>> able to test this at the moment, but I would think that this would give
>> you CR
>> then CR LF (oa od oa).  If it says that the record delimiter is a new line
>> by
>> default, then it sounds like the documentation should be updated to
>> reflect the
>> fact that you need to specify the r=\n to get the newline.
>>
>> Jeff Harrison
>> jeffaharrison at yahoo.com
>>
>>
>>
>> _______________________________________________
>> Filepro-list mailing list
>> Filepro-list at lists.celestial.com
>> Subscribe/Unsubscribe/Subscription Changes
>> http://mailman.celestial.com/mailman/listinfo/filepro-list
>>
>
>
> --
> Nancy Palmquist         MOS & filePro Training Available
> Virtual Software Systems    Web Based Training and Consulting
> PHONE: (412) 835-9417           Web site:  http://www.vss3.com
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.celestial.com/pipermail/filepro-list/attachments/20101119/2751fb0c/attachment.html 


More information about the Filepro-list mailing list