[Home] [By Thread] [By Date] [Recent Entries]
David Carlisle wrote:
As I suspected, it was my own bug. I was applying a normalization function to my lookup string before doing the lookup, which for reasons that are still unclear to me, was producing strings, in most cases, that did not match the keys in the table. Removing the normalization fixed the problem. Cheers, Eliot -- W. Eliot Kimber Professional Services Innodata Isogen 8500 N. Mopac, Suite 402 Austin, TX 78759 (214) 954-5198 ekimber@xxxxxxxxxxxxxxxxxxx www.innodata-isogen.com
|

Cart



