Hello,

Mr. Wagner, you are right, some keys in hashA are not in hashB, this means the perl 
from the previous step also needs debugging or I have some spurious data. This would 
explain why when I used 'if defined' in addition to, what Mr. Dixon  suggested,
and which is what Mr. Bakken is now suggesting, the error messages disappear.

I would have never guessed the reason for the error messages, since I was absolutely 
certain all keys in hashA are present in hashB, but I now realize that is not the case.

Thanks to everyone for the help.
Aim



======================================================
"Wagner, David --- Senior Programmer Analyst --- WGO" wrote:

> Aimal wrote:
> > Hi,
> >
> > Thanks for your help, it seems to be doing the job and in a fraction
> > of the time. You are right about the keys and values being the same-
> > that was an error, the hash is arranged as you have said ( '12345' =>
> > '67890'). There seems to be a slight error, the following error
> > messages appear on numerous occasions, line 83 is the print
> > statement, also some of the values in the outfile have no keys? I
> > cannot see why it is giving the error messages:
> >
> > Use of uninitialized value in hash element at prepare.pl 83.
> > Use of uninitialized value in concatenation (.) or string at
> > prepare.pl line 83.
> >
> >    foreach my $keyA (keys hashA) {
> >         my $keyB = $hashC{$keyA};
> >       print "$keyA\n$hashA{keyA}\n\n$keyB\n$hashB{keyB}"
> >     }
> >
>         Can there be keys in hashA which don't have a key in hashB? If this is true, 
> then that is why you are getting the msgs coming up. If they are supposed to exist, 
> then you might need to put in some debugging prints to see what is going on.
>
> Wags ;)
>
> **********************************************************
> 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]

Reply via email to