Re: The " character in CPYFRMIMPF

[Tom Jedrzejewicz <tomjedrz@xxxxxxxxx>]

I concur - this is a user error, selecting as delimiter a character
used in the data.

Sometimes newbies to EDI will do the samething; they will want to use
* or & or # as a delimiter so the messages can be eyeballed.  Then one
of those characters ends up in the data, and voila, same problem.

That said, having them replace " with in is probably the best quick solution!


On Wed, 29 Sep 2004 16:33:54 -0400, Douglas Handy <dhandy@xxxxxxxxx> wrote:
> Rob,
> 
> > Perhaps so, but a bugs a bug and I still recommend reporting it to IBM.
> 
> I don't think I can call this a bug.  There are no well-defined
> industry standards for CSV formatting.  That is why MS can get by with
> Excel's abhorent behavior of having any value which looks like a
> number be construed as a number even when it is in quotes.  This
> absolutely wrecks havoc with trying to import USA 5-digit zip codes
> when using CSV extensions.
> 
> I believe both Excel and CPYFRMIMPF will handle consecutive (i.e.
> doubled) quote as in "15"" PIZZA", much like you'd say 'o''clock' in a
> RPG literal.  I'd argue that the CSV contents is faulty, even if Excel
> will accept it.
> 
> Doug
> 
> 
> --
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
> To post a message email: MIDRANGE-L@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l
> or email: MIDRANGE-L-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/midrange-l.
> 
> 



-- 
Tom Jedrzejewicz
tomjedrz@xxxxxxxxx