Export file and the use of Append -a

[Dennis Malen]

I don't know why. I have been using that definition for years. Forgot where
I got it from. Which r/ should I delete? Will that effect or fix the append
problem??

Dennis
----- Original Message -----
From: "Jean-Pierre A. Radley" <appl at jpr.com>
To: "FilePro Mailing List" <filepro-list at seaslug.org>
Sent: Wednesday, October 13, 2004 5:37 PM
Subject: Re: Export file and the use of Append -a


> Dennis Malen propounded (on Wed, Oct 13, 2004 at 05:14:35PM -0400):
> | This is my problem. I have clients that I report to with the use of an
> | Export Ascii file. The files could be one of three types:
> |
> | 1. Fixed Length
> | 2. Tab Delimited
> | 3. Comma Delimited
> |
> | The following are my definitions for each:
> |
> | 1. export ascii rnf=(pn) r=\r r=\n -x -a
> | 2. export ascii rnx=(pn) r=\n f=\t -a
> | 3. export ascii rna=(pn) r=\n f=, o=" c=" -a
> |
> | The problem is that when we attempt to append to (1) (the fixed length)
it
> | rewrites the file. It does not append. Comma delimited (3) works fine
and
> | Tab delimited (2) works on one client file and does not append to
another
> | client file. The Tab delimited works fine in other processing that I
have so
> | that is probably something I'm doing wrong in the processing (Maybe).
> |
> | My immediate concern is the Fixed Length (1). The append (-a) does not
seem
> | to work. Does anyone see what I am doing wrong with the -a in the Fixed
> | Length (1) definition.
> |
>
> Why are you defining 'r' twice in No. 1?
>
> --
> JP
> _______________________________________________
> Filepro-list mailing list
> Filepro-list at lists.celestial.com
> http://mailman.celestial.com/mailman/listinfo/filepro-list
>
>