Jay Savage wrote: > One day, I'll start remembering this ist doesn't set reply-to... > > On 2/22/06, Jay Savage <[EMAIL PROTECTED]> wrote: >> On 2/21/06, Wagner, David --- Senior Programmer Analyst --- WGO >> <[EMAIL PROTECTED]> wrote: >>> Timothy Johnson wrote: >>>> I don't have time right now to run it, but I notice that you left >>>> out the portion of the code in LABEL2: where you actually print >>>> whether or not it worked. Is it possible that it really is >>>> working but you forgot this line? >>>> >>>> printf "<--Comma hit!!"; >>>> >>>> Sorry if that seems like a stupid question, but I've gotten stuck >>>> on worse. >>>> >>> >>> No. The second is an actual Production script and as it >>> does the split and checks the data , it fails because the comma was >>> still in the code. That is why I know it fails. >>> >>> Wags ;) >>> >> >> Wags, >> >> Your error is someplace else: the supplied code works fine for me, >> although it seems a bit convoluted. >> >> I don't see where you're actually printing the output to file, maybe >> you're grabbing it too early in the loop? Or printing the wrong >> variable? It also looks like you're expecting this data to be passed >> around from system to system--else why look out for \r?--maybe you're >> having other encoding issues. Are the double quotes being stipped >> as they're supposed to? >> >> Also, print out $. every time through, as well as $_ in both while >> loops. Make sure the program is seeing the data you think it's >> seeing. My gut reaction is that if a script works with data from >> __DATA__ and fails with a file, the problem is with the file. In >> particular, try opening the file :crlf instead of trying to handle >> the line endings by hand. Make sure you don't have embedded control >> characters in the data (if you read the file with cat or even emacs, >> you may see the infamous ^M in the middle of the lines somewhere), >> etc. >> >> Also, make your life easier and grab a copy of Text::CSV.
True, but I don't have the control I prefer over my prod and test locations. So I try to use what I have and keep the loads of modules to minimum. What I found out was that I was missing a chuck of data processing which needed to have the same code placed there. I corrected that and all is working as it should be. Yes, I am playing with \r, but I am ftp'ing from one sun box to another, but I end up with a return and the std carriage return and linefeed. Where I am getting the data is a third party application but they seem to be at the Windows world than Sun arena. That is my take on it, but for me until my Sys Admin can see what if anything can be done, I replace the \r with nohting and all is working as it should. Working harder than I should, but at least working. I thank the list for the up and suggestions you provided. Made me look again and see that enemy is ME and not Perl. Which what it usually is. Wags ;) >> >> HTH, >> >> -- jay >> -------------------------------------------------- >> This email and attachment(s): [ ] blogable; [ x ] ask first; [ ] >> private and confidential >> >> daggerquill [at] gmail [dot] com >> http://www.tuaw.com http://www.dpguru.com http://www.engatiki.org >> >> values of ? will give rise to dom! ******************************************************* This message contains information that is confidential and proprietary to FedEx Freight or its affiliates. It is intended only for the recipient named and for the express purpose(s) described therein. Any other use is prohibited. ******************************************************* -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] <http://learn.perl.org/> <http://learn.perl.org/first-response>