I just noticed that History is a reserved word, so thought it would be better to exclude the possibility of this having something to do with the error (but that's just a speculation).

>Using another alias wouldn't be easy, as there are 120+ references to it. There some advantage to making that effort?
>
>>>Any ideas how it is possible to get this error, when the "cursor" referred to is actually a shared DBF?
>>>
>>>The error occurs on this line:
>>>

REPLACE Endtime WITH ltTime IN HISTORY

>>>
>>>where HISTORY is a shared DBF. Now, curiously, this code is executed a few hundred times a day, and has been for months ... and I've gotten this error (#111) once yesterday and once today.
>>>
>>>Ideas?
>>
>>Just in case, can you open this table under different alias to not confuse with the reserved word?