In this case, the data specs are very detailed and no commas allowed in the data itself. For example, no $ or other non-alpha or non- numerical characters.

In many EDI documents, commas are allowed but then the field delimiter is not a comma. This particlar instance is not a true EDI document, at least to any reconized standard.

I am happy to say I was able to create the exact file they requird and I needed with just the one FileGateway command. Very clean and efficient. Just took a couple of suggestions from the list to steer me in the right direction.


Bob Thompson
LaPorte, IN
219-363-7441

Sent from my iPod

On Mar 31, 2011, at 8:51 AM, James Bentley <[email protected]> wrote:

Bob,

I am curious. What is your export supposed to look like if one or more of the exported fields contain a comma in the raw data? My understanding is that the data should be quoted (singe or double quotes) if field contains a comma.
Or perhaps the big box stores fields prohibit commas.

Jim Bentley
American Celiac Society
[email protected]
tel: 1-504-737-3293


From: "[email protected]" <[email protected]>
To: RBASE-L Mailing List <[email protected]>
Sent: Wed, March 30, 2011 10:08:54 AM
Subject: [RBASE-L] - Re: CSV and Null unload question

Bob:  I'm going to keep your solution in my notes!

Karen



Close!  However double quotes popped up using the CSV option.

Example using the Gateway Export CSV with Blank_if_zero  on



"IN","661","No",100,,,,,,"$28.39",,,,,,,"100016842","THEHOMEDEPOT",



However, I was able to get it to work using

Gateway Export TAB  with Blank_if_zero and SEPARATOR , options.



IN,661,No,100,,,,,,$28.39,,,,,,,100016842,THEHOMEDEPOT,





This big box store is very particular and the format has to be exactly as they

dictate. A pure comma separated file with no quotes, no null characters, etc.



Thanks for the input,

-Bob






Reply via email to