CSV export issues

[Jean-Pierre Radley]

Brian K. White averred (on Mon, Jul 10, 2017 at 03:11:05PM -0400):
| 
| 
| -----Original Message-----
| From: "Jean-Pierre Radley via Filepro-list" <filepro-list at lists.celestial.com>
| Sent: Friday, July 7, 2017 5:58pm
| To: "filePro Mailing List" <filepro-list at lists.celestial.com>
| Subject: Re: CSV export issues
| 
| 
| Thanks for all the suggestions.
| 
| 
| You cannot use the double-quote (chr("34") as an argument in filePro.
| 
| If you try
| 
| 	c=chr("34")
| 
| c comes back empty.
| 
| You can't use chr("34") in expressions for functions like INSTR, MID,
| STRTOK, XLATE, oe MID.
| 
| But I still found a pot at the end of my rainbow, by changing
| 
| 	export word rpt=/usr/tmp/report.csv
| 
| to
| 
| 	export ascii rpt=/usr/tmp/report.csv r=\n f=,
| 
| That still leaves the trivial issue of editing strings containing
| commas, but I now have a CSV file which contains output like
| 
| 	1-1/4" 2FL W/ 3/4" SH
| 	3/4" 4FL SEEM CARB 7"OAL
| 
| ------------------
| 
| 
| Perhaps c = "\"" would have worked, I was just trying to play it safe because I don't *think* that would work, and, store the value to use it a zillion times rather than running a function to generate it a zillion times.
| 
| I am not in a position to double check myself directly right now, but I am very skeptical that you can't  c = chr()  ?? really??? I could *swear* we've done that countless times for backslash (97 I think?) and other chars.
| 
| I will have the take your word for it for now I guess, and It's good you got around it anyway.
| 
| -- 
| bkw

You can succeed with c=chr(NUM) for many values of NUM, but 34 isn't one of
them.

-- 
JP