#in lookup causing problems?

[Jay R. Ashworth]

On Fri, Jan 02, 2004 at 04:55:30PM -0500, Walter Vaughan wrote:
> Kenneth Brody wrote:
> >Walter Vaughan wrote:
> >>This code fragment seems to work just until I pass it variables
> >>that contain the # (pound variable)
> >>    
> >>
> ><snipped>
> 
> >"#55" is not a valid number.  What would you expect it to find when
> >you did a lookup based on a numeric field?
> >  
> >
> the lookup to fail (as in "not foo_bar" to be true) as it does if passed any
> other kind of value like "12V".
> 
> Are you trying to say if you pass a value that starts with a pound key, the
> proper thing for filePro to do would be to select the first value in the
> index?

IMHO, the edit should force #55 into a ... *I've* got it.

Ken: you're using the wrong routine there.

The integer parsing routine that's getting called is the one that
translates numbers in print codes... which might have a prefix to make
them look like they're in a different number base.

...

Naw; damn; that can't be it either, 55 isn't equal to 43 for any
combination of octal, decimal, *or* hex.  Crap.

I'll go back to "it should see the illegal character and blank the
field".  :-)

Cheers,
-- jra

-- 
Jay R. Ashworth                                                jra at baylink.com
Member of the Technical Staff     Baylink                             RFC 2100
The Suncoast Freenet         The Things I Think
Tampa Bay, Florida        http://baylink.pitas.com             +1 727 647 1274

        Come see Linux Gazette in our new home: www.linuxgazette.net!