>Hi there,
>
>some of our customers are getting a lot of index-errors 2066. To most of them it happens always
>in the same routine/module, always the same dbf, but to each customer it happens in another routine.
>The error happens when it comes to querying a dbf and I can reproduce in the command window.
>It is strange how it appears, for example I have a simple query which goes like that:
>
>

>select * from galtrans where nummer = "1111111111111"
>

>
>This works fine, but trying it with the identified "troublemaker" causes the error
>
>

>select * from galtrans where nummer = "2222222222222"
>

>
>This causes error 2066 to happen
>
>But funny enough, if I set the order to "nummer" (there is an index on this field) and start a seek on this number, everything
>works fine.
>If I reindex, the problem is solved, but it happens with another record in thsi table.
>
>All Customers which encountered this problem habe one thing in common. They use Win7-PCs,
>mostly in combination with XP-PCs. What we already did, is to deactivate the smb2-protocol on the Win7-PCs and
>deactivate the write-cache to.
>
>I am at the point where I do not know what to do next, so here are two questions:
>
>1) Has anybody encountered the same and has some hints for me?
>
>2) How can I check, if the index is corrupted. I tried the needreindex-function from my Stonefield
>Database Toolkit but this function does not detect the corrupted index.
>
>Thanks in advance
>
>Thomas

Hi,

What is the index expression on field nummer and maybe also other index expressions where field nummer is involved?

Regards,

Koen