RE: The " character in CPYFRMIMPF

I guess the question I have is, is it necessarily a bug?  Sure, Microsoft
handles it appropriately for this given situation.  But, then, Microsoft's
been known to blow off standards.

I dunno; just wondering.

Frankly, I have never liked dealing with " and , as CSV text quotes &
delimiters.  At a minimum, a delimiter should be an untype-able character,
something like x'00' or x'FF'; don't know if that does weird stuff
translating from EBCDIC & ASCII and vice versa.  But, when dealing with
outside sources, you don't always get to pick your choices.

db

> -----Original Message-----
> From: midrange-l-bounces@xxxxxxxxxxxx / rob@xxxxxxxxx
> Sent: Wednesday, September 29, 2004 3:37 PM
>
> Perhaps so, but a bugs a bug and I still recommend reporting it to IBM.
>
> Then again, your first field might have a leading double quote and your
> last field might have a trailing double quote, providing those fields
> aren't numerics.  And if you have two numerics together how do
> you replace
> that comma with a hex zero delimiter and not replace an intentional comma
> mid field?  Or if someone has a field like this
> "test,","next field",9,2,"I,love,freedom,fries","quote the raven, "never
> more"","final field"
> would that become
> "testX'00'X'00,9,9X'00'...
>
> Rob Berendt