Interesting observation, I haven't thought about it, though table doesn't have deleted records...

>Possibly, deleted records interfere. In this case, you have to filter the index on "not deleted()".
>
>>Hi everybody,
>>
>>I have a file with primary index filename+rcode+town+extryear+extrweek.
>>
>>Before appending records to this file from log file, I run the following code:
>>

>>set talk on
>>set talk window noshow
>>
>>select LogFile.FileName from (m.lcLogFile) LogFile ;
>>         inner join BatchCntrl btch on ;
>>      LogFile.FileName+LogFile.rcode+LogFile.Town+LogFile.ExtrYear+LogFile.ExtrWeek = ;
>>         btch.FileName + btch.rcode + btch.Town + btch.ExtrYear + btch.ExtrWeek ;
>>         group by 1 ;
>>         into cursor curCheck
>>set talk off
>>lnTally = _tally
>>if m.lnTally > 0 && It should not happen

>>
>>* this is a bad case
>>endif
>>However, periodically we have error message, which is trapped by our Error Handler, that uniqueness of indexes in BatchCntrl table is violated.
>>
>>I guess, I can change this code to do select from log where in (select from Batch..)
>>
>>But just out of curiosity, why this code doesn't work as I think, it should?
>>
>>Thanks in advance.