>>>We have just 134 tables <g> Few have bad indexes. I produced an XLS with all indexes in our tables...
>>
>>Well, the error is likely to happen on a specific table, so you might concentrate on that one first. But then, of course, it is best to sometimes do some systematic reviews, if you know something is likely to be wrong.
>
>No, the error occurs in different places. In my version of the program the error is eliminated, so the problem could be somewhere else. But we're not switching to my version and I do not know what change eliminated the error, so we still have to work on the problem.

I'm curious to learn how you know the error is eliminated yet you don't know what change eliminated the error.

Jim