Joe,
First, as Steve said, check back over recent posts on the PDox NGs -
we've covered all this stuff many many times...
> I've got a txt file with fields delimited by commas. One field contains
> product descriptions, and many have words enclosed in quotation marks.
If the FULL Alpha-FIELD is enclosed/delimited by ONE Double-Quote-mark
at both ends of the fields, then that's perfect. Eg:
123,456,"alpha field",789
If there are embedded DOUBLED double-quotes WITHIN some alpha-fields,
then that's perfect also. Unfortunately, the Paradox CSV drivers are
cr*p, and don't understand this. You should follow Rodney's advice. Eg:
123,456,"Large 10"" bolts",789
If there are embedded SINGLE double-quotes WITHIN some alpha-fields, and
double-quotes are NOT used as alpha-field delimiters, you should check
those CUSTOM script options, in case you can get a combo that suits your
files. Eg:
123,456,'Large 10" bolts',789
If there are embedded SINGLE double-quotes WITHIN some alpha-fields, and
double-quotes ARE used as alpha-field delimiters, then you're in (deep?)
caca. Presumably, that file also came OUT OF a broken Paradox CSV
driver! Eg:
123,456,"Large 10" bolts",789
Worse, if there are adjacent commas near those embedded double-quotes,
you're in very very deep.... Eg:
123,456,"Large 10", and 15" bolts",789
In my PDox apps, I have a separate utility that I run on all CSV files
going into Paradox, and on all CSV files coming out, to address all the
above issues. It's all a major PITA...
- Mike
|
