Earl,

I assume that the records that are no longer found are NOT the ones you deleted.

Your INDEX expression seems odd. Are you running with SET NEAR ON? If not, can you provide a proper example of the SEEK command AND the expression CONTENT that you are seeking on? For instance, don't just show me: SEEK m.LastTimeIn but show me the content of m.LastTimeIn.

Have you changed the DATE display setting in Windows SINCE you built the index?

Your INDEX would work with much better reliability if you used TTOC(TimeIn, 1)+cID
Of course you would also have to ensure that your SEEK argument was built in the same manner.

good luck



>>Earl,
>>
>>1) Did you just delete the records or did you PACK the table afterwards?
>
>I deleted and then Packed.
>
>>2) What do you mean by "...this operation hammers the index."?...
>What 'operation'?... By 'hammer' do you mean breaks or do you mean seems to read it inordinately muchly?
>
>By hammer I mean that it no longer finds the records in the index.
>
>
>>3) What version of VFP7 are you running - original or SP1?
>
>VFP7.0 SP1
>
>>4) What are your EXACT
>>---a) index TAG expressions;
> index is a regular index named cUser = TTOC(timein)+cID
>>---b) command that 'hammers' the index?
> seek no longer works
>>
>>good luck
>>
>>
>>
>>>Hi,
>>>
>>>I have a table that has 2 indexes. All this table does is track the login and logout times of the users. I went in and deleted a bunch of old records and then it quit working. It appears that this operation hammers thes index. Any ideas what might be causing this. I just switched the app from VFP5 to VFP7 if that matters.
>>>
>>>Thanks,
>>>Earl