>>>>>Yes, I also suspected index corruption.
>>>>
>>>>Meneer Meester was definitely not referring to index corruption.
>>>>
>>>>A corrupt index would give you wrong results.
>>>>
>>>>An unbalanced index would give you correct results, but it may be very slow in doing so.
>>>>
>>>>I suspect that a REINDEX should be enough to correct this situation.
>>>>
>>>>Hilmar.
>>>
>>>I can not do it. This operation should be done directly on the server. :(((
>>
>>And yet, the explanation of Walter makes perfect sense; and REINDEX seems the only way to make the query faster.
>>
>>Can't you send a small maintenance program, to be used on the server?
>>
>>Or at least get a copy of the database to test locally, to test Walter's hypothesis?
>>
>>Hilmar.
>No to all questions.
>
>But I solved the problem already. The problem just was in another place, not the one, I was trying so hard to fix. In few other places there was LOCATE command instead of SEEK and this caused all the troubles. Once I fixed it, it now works fine.
>
>I'll send you the site in private to test for yourself. What version of IE do you have? It doesn't work correctly on my IE 5. Also the guys didn't include your translations despite all my efforts and that's a pity :(
>
>Anyway, check your private in a minute.

Nadya;

For some time I complained about the inconsistencies between I.E. 5.0, 5.5 and 6.0. I created a list of such information and finally talked to someone at Microsoft. The answer I got was, “There are bugs in I.E. 5.0 which allow certain things to work that should not and other things to not work correctly”. I am glad I am not crazy but this is a part of my term “Browser Experience”. The Desktop works in a much more consistent although not always perfect manner. We will avoid discussion of any other browser. Why upset the weekend? :)

Tom