Thanks again to everyone! I took some advice and downloaded "Synalyze" to check the file in Hex format. Having been over ten years since opening a file in Hex mode (and even then not knowing what I was doing!) I was pleasantly surprised at how quickly I was able to figure out how to do a search and understand the results (Thanks to Patrick for the in-depth "mini-tutorial" on what to look for!).
As strange as it sounds (and I don't have a clue yet as to how), the file was getting "changed" when either sent via email or opened on their end. They were indeed seeing duplicate carriage returns on their end (Even in a Hex editor) where on my end they were not there! Go figure! Again, Thanks for all the great responses and help! James Sheffer, The HigherPowered Team! On Aug 16, 2012, at 6:52 PM, Patrick Woolsey <[email protected]> wrote: > At 16:20 -0500 08/16/2012, Jim Sheffer wrote: > [...] >>> b) When you open the .csv file in BBEdit, what is its line ending format? >> >> Windows - which is what I need. > > OK; that means the generated file is almost certainly correct. > > >> I think I've found the problem. The file was actually sent to my client, >> then on to the company who created the system they are using. >> I checked with my client and there file is also fine (no extra carriage >> returns. It seems the company they sent it to opened in up in note pad >> lite and somehow IT is creating the extra carriage returns. >> > > Wups :-) > > >> Of course they are saying it is me, so I wanted to make sure absolutely >> before I tell my client that the company is full of it :-) >> They have been a pain for both me and my client over this and it is quite >> annoying! >> > > Sounds like you're on solid ground here but understood. > > >> David- - I ran the file via terminal through hexdump with no problem. Can >> you tell me what I'm looking for? >> > > I can give you a quick example as well. > > First, for reference, "0D" is the hex value of a carriage return (CR, ASCII > 13), and "0A" is the hex value of a line feed (LF, ASCII 10). > > So, a CRLF pair would be "0D 0A", while two CRs in succession would be "0D > 0D", etc. (The space in between is just for readability in the hex dump > output; it's not significant.) > > Say you have a file with Windows line endings which contains this text: > ==== > the quick red fox > jumped over the lazy brown dog > > ==== > and here's the resulting hex dump output: > ==== > 0000: 74 68 65 20 71 75 69 63 6B 20 72 65 64 20 66 6F the quick red fo > 0010: 78 0D 0A 6A 75 6D 70 65 64 20 6F 76 65 72 20 74 x..jumped over t > 0020: 68 65 20 6C 61 7A 79 20 62 72 6F 77 6E 20 64 6F he lazy brown do > 0030: 67 0D 0A g.. > ==== > > You can now look and/or search* within this output for the expected line > break characters or character pairs, e.g. > > 0000: 74 68 65 20 71 75 69 63 6B 20 72 65 64 20 66 6F the quick red fo > 0010: 78 0D 0A 6A 75 6D 70 65 64 20 6F 76 65 72 20 74 x..jumped over t > ***** ** > here's the CRLF pair which ends the first line of text, and > > 0030: 67 0D 0A g.. > ***** ** > here's the CRLF pair which comes at the end of the file. > > [* Note that because of the output formatting, the CR could appear at the > end of one report line and its following LF at the start of the next report > line.] > > > Regards, > > Patrick Woolsey > == > Bare Bones Software, Inc. <http://www.barebones.com> > P.O. Box 1048, Bedford, MA 01730-1048 > > -- > -- > You received this message because you are subscribed to the > "BBEdit Talk" discussion group on Google Groups. > To post to this group, send email to [email protected] > To unsubscribe from this group, send email to > [email protected] > For more options, visit this group at > <http://groups.google.com/group/bbedit?hl=en> > If you have a feature request or would like to report a problem, > please email "[email protected]" rather than posting to the group. > Follow @bbedit on Twitter: <http://www.twitter.com/bbedit> > > > -- -- You received this message because you are subscribed to the "BBEdit Talk" discussion group on Google Groups. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at <http://groups.google.com/group/bbedit?hl=en> If you have a feature request or would like to report a problem, please email "[email protected]" rather than posting to the group. Follow @bbedit on Twitter: <http://www.twitter.com/bbedit>
