OK, I guess that makes some sense, I guess. However, none of the three possibilities you mention hold true; that is, the table certainly is not read-only, there's plenty of room on the disk, and the same user uses the program all day long, as there are 100's of such REPLACEs done daily.

So, your statement of "for some reason VFP can't save the data" makes sense, I just don't understand an error that happens so sporadically.

Thanks anyway

>>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?
>
>It is the same error message for a cursor or a table. It appears if for some reason VFP can't save the data to disk.
>
>The cause is frequently a read-only table. Other things to watch out for are disk full, and access rights on a network (you might be allowed to read, but not to write).