Default however, SET EXACT or SET ANSI should not matter. The fields are CHR(3) and the variables in the seek() are len() = 3 and there is only one possible match for any given combination of country+code


>>We have an old app that is going bonkers. We have a lookup table that has an index using two fields. country+code
>>
>>Every country is fine when doing a seek(m.country+m.code,"table","IDX")
>>
>>One country, "115" fails the seek when the m.code = [3EZ] or [36Y] or [1EZ]
>>
>>If the m.code is [LA1] it passes the seek().
>>
>>The table has been reindexed several times. The values being passed to the seek() function are the right type and length. The records exist in the lookup table AND the seek() works every time when stepping through the debugger.
>>
>>Can anyone think of a reason the seek would fail at run time but not at the command window or in the debugger?
>
>SET EXACT is?
>SET ANSI is?