lookup wackiness
Fairlight
fairlite at fairlite.com
Mon Nov 10 11:55:23 PST 2008
Explain this, if you can...
* Index field based on field with (8,RJFILL0) cast.
* Key field that was uncast, but had 8 characters.
Lookup fails in -most- cases (77889908, 00000abc, 00000001, etc.) that
still match the actual data in the index field of the lookup.
Lookup SUCCEEDS on 00000111 for value.
Casting the key field to (8,RJFILL0) fixes the problem of spurious
failures.
Whacked. It should either work or not, but not "sometimes".
Moral: Fail to cast your lookup key fields at your own peril.
(Apparently. First time it's ever bitten me.)
mark->
--
"I'm not subtle. I'm not pretty, and I'll piss off a lot of people along
the way. But I'll get the job done" --Captain Matthew Gideon, "Crusade"
More information about the Filepro-list
mailing list