RE: Re: help on searching a file

Ahhh, much more readable...

It's still difficult (impossible?) to guess what, exactly, is going wrong. Can you give us a little more information? When you say "...the script only gets the cable modem value...", what do you mean by 'the script'? Which variable? Do the rest match?

You may also need to post a bit more of the code, to see if variables are getting clobbered by some of your subroutines.

Comment on RE: Re: help on searching a file

Replies are listed 'Best First'.
RE: RE: Re: help on searching a file by DaWolf (Curate) on Sep 12, 2000 at 22:09 UTC
All the other fields from the FORM are ok. And I've tried the "stupid way" - like: `print MAIL "$FORM{'ba'}";` [download] for each line of the datafile instead of using the foreach loop, and it didn't worked. Er Galvão Abbott a.k.a. Lobo, DaWolf Webdeveloper	[reply] [d/l]
RE: (Guildenstern) Re: help on searching a file by Guildenstern (Deacon) on Sep 12, 2000 at 22:20 UTC
Well, if doing that way still didn't work, I would suggest at least showing us the code where the FORM hash gets populated. It sounds like at least some of the values aren't being set up right. Guildenstern Negaterd character class uber alles!	[reply]
RE: (Guildenstern) Re: help on searching a file by Guildenstern (Deacon) on Sep 12, 2000 at 22:05 UTC
Yes. More code and a better error description are needed. I thought I had found something in the use of $FORM. Apparently this needs to stay in the code, but we have no idea how that hash is being populated. If you're getting nothing out of the statement `$FORM{$qid}`, then the cause may be in the %FORM hash, or may be something as simple as what tye suggested - having newline characters hanging off the end of `$qid`. Guildenstern Negaterd character class uber alles!	[reply] [d/l] [select]