Thanks Sergey for your reply.
I have recreated the indexes and will check this evening if this sorts the problem.
If it was a corrupt index, I would have expected to see more (rathet than very intermittent) problems

Regards,
Gerard



>In my experience only corrupted indexes could cause incorrect SEEK results.
>
>BTW, you can shorten code by using SEEK() function
>

>IF SEEK(Cur.MyField, "MyLookup", "MyOrder")
>  Do something
>ENDIF
>

>
>
>>I have an app where it appears that a Seek is not working intermiitently.
>>I have a table as follows:
>>
>>Cur.MyField
>>-----------------
>>A
>>B
>>C
>>D
>>
>>Which seeks another table
>>Scan
>> X=Cur.MyField
>> Sele MyLookup
>> Seek X Order MyOrder
>> If Not eof()
>> Do something
>> Endif
>>Endscan
>>
>>The seek on the third line of the Table above (C) sometimes gets a wrong record (e.g. might get B instead)
>>This happens very infrequently (Maybe Twice a day out of 5,000 seeks)
>>The Table taht is being Looked up is Locked ( as data nay be inserted and amended)
>>The Lookup Table has about 30,000 records , with about 40 fields
>>
>>As a general rule,Seems to be happening on very busy period of the day, and also near break times(e.g. Lunch time, End of day)
>>
>>This is only happening in one place in a fairly large APP.
>>Has anybody come across any issues like this ...I have reengineered the code and tried all sorts but
>> it still seems to be intemittently getting a wrong Seek
>>
>>Tia.
>>regards,
>>Gerard