CSV export issues

Scott Nelson scott at logicdatasystems.com
Sun Jul 2 10:05:18 PDT 2017


I stopped doing CSV because of the issues with commas and quotes.  I do 
Pipe delimited files, save them as .pi or .txt and give the customer 
instructions on importing into excel.

export word rpt=(f) is the correct sytax, but you don't want @td since 
it has slash in it.



On 07/01/2017 03:44 PM, Jean-Pierre Radley via Filepro-list wrote:
> I am trying to generate a spreadsheet using
>
> 	export word rpt= /usr/tmp/report.csv
>
> The filePro file is an inventory of metal parts. In the Description
> field the single or double quote may show up as the conventional
> abbreviation for feet or inches, e.g.:
>
>          6" DIAL CALIPER WHITE FACE
>
> Whenever this happens, processing goes nuts at the quote-mark: all the
> fields of every record up to the next one with a quote-mark are output
> on the same line of the CSV file.  If there are over 600 records between
> two fP records with a quote mark, the CSV file will have a line with
> over 600 columns.
>
> I can of course use an edit to remove the quote-marks, but is there some
> way to use some escape mechanism to preserve them in the CSV?
>
> Another minor annoyance:  I wanted to define the output file from data
> in the filePro input. Say field 1 is the customer number:
>
> 	f = 1 { "-" { @td; export word rpt=f
> or
> 	f = 1 { "-" { @td; export word rpt=(f)
>
> Neither works.
>




More information about the Filepro-list mailing list