Re^3: Parse one fiile, send the records to two different files

Replies are listed 'Best First'.
Re^4: Parse one fiile, send the records to two different files by BigRedEO (Acolyte) on May 27, 2016 at 17:16 UTC
Well, the script now ran through and again put only the correct files in my "clean" file, but for the error file, I now have 1138 lines, where I should only have 272 lines. When I did a "head" on that error file, I find that it's listing each field as a separate line and no comma delimiters i.e. - 650187016 2 1 checked out under cash 650200678 1 1 HIT CASH TWICE 650096506 1 whereas I want the lines put back in their original form, all commas included, i.e. 650187016,2,1,checked out under cash ,,,,,,,,,,,,,,,,,,,,,,,,,,,,	[reply]
Re^4: Parse one fiile, send the records to two different files by BigRedEO (Acolyte) on May 27, 2016 at 17:24 UTC
Nope! STILL didn't work! Now it jumbled it all the fields from the "error" records together into one just line with spaces and no commas. My errorFiles.csv has just one line with every field from the error records. `if (!length $fields[28]) { print $ERR_FH join (',', $_) for @fields; } else` [download] ...is what I'm using. So what else could be missing?	[reply] [d/l]
Re^5: Parse one fiile, send the records to two different files by BrowserUk (Patriarch) on May 27, 2016 at 18:32 UTC
You need `print $ERR_FH join (',', @fields );` With the rise and rise of 'Social' network sites: 'Computers are making people easier to use everyday' Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error. "Science is about questioning the status quo. Questioning authority". I knew I was on the right track :) In the absence of evidence, opinion is indistinguishable from prejudice.	[reply] [d/l]
Re^5: Parse one fiile, send the records to two different files by stevieb (Canon) on May 27, 2016 at 18:33 UTC
meh... I think the problem is with how we're using `join()`. I overlooked the fact that its second parameter should be the list. Try the following (note that you may still need to use `chomp()` on the array as mentioned in Re^5: Parse one fiile, send the records to two different files): `print $ERR_FH join(',', @fields);` [download]	[reply] [d/l] [select]
Re^6: Parse one fiile, send the records to two different files by BigRedEO (Acolyte) on May 27, 2016 at 18:51 UTC
So close - all the commas are now back in, but it's still putting all the fields in as one big long sole record.	[reply]
Re^7: Parse one fiile, send the records to two different files by stevieb (Canon) on May 27, 2016 at 18:58 UTC
Re^7: Parse one fiile, send the records to two different files by poj (Abbot) on May 27, 2016 at 19:00 UTC
Re^8: Parse one fiile, send the records to two different files by stevieb (Canon) on May 27, 2016 at 19:01 UTC
Re^8: Parse one fiile, send the records to two different files by BigRedEO (Acolyte) on May 31, 2016 at 20:17 UTC
Re^5: Parse one fiile, send the records to two different files by stevieb (Canon) on May 27, 2016 at 18:25 UTC
Does chomp on the array reflect in any change?: `if (!length $fields[28]) { chomp @fields; print $ERR_FH join (',', $_) for @fields; }` [download]	[reply] [d/l]
Re^6: Parse one fiile, send the records to two different files by BigRedEO (Acolyte) on May 27, 2016 at 18:32 UTC
No - that did not do it either. It's as if it's not joining the fields back together with the commas to print each line. It's still writing every field that is not empty into the errorFiles.csv with a space in between each field as one continuous line.	[reply]
Re^4: Parse one fiile, send the records to two different files by BigRedEO (Acolyte) on May 27, 2016 at 17:19 UTC
Wait - never mind! Think I caught what else I left in that statement that caused the problem. Am running it again now to verify.	[reply]