>Hi,
>If Volume shadow copy is enabled, it is what would be causing the problem, it should be disabled.
>Any Snapshot type process can corrupt the DBF's or greatly hinder performance, especially when the user thinks the app has frozen due to apparent inactivity when it is waiting for the snapshot process to complete and restarts the workstation.
>The user won't tell you that they have restarted the workstation unless you ask the question.
>Snapshots do not work well with apps that aren't snapshot aware and also don't work well on highly loaded systems and should be disabled.

Thanks. That's several votes for something along these lines.

Tamar
>
>>I have a client where at least one person (one of the testers, so intense user of the app) is intermittently getting error 111 "Cannot update the cursor "cursor", since it is read-only." He says he sees it at least once every other day.
>>
>>The error log tells me that it's always the same table and always on the ZAP in this sequence:
>>
>>

>>USE Network EXCL
>>ZAP
>>USE Network
>>

>>
>>This is in a routine that does the same thing to about 10 different tables and this is not the first one listed. (And no, I didn't write this code originally and wouldn't have done it this way, but changing the architecture at this point would be significant.)
>>
>>This is a DBF permanently stored on disk, not a cursor, and not a table created temporarily.
>>
>>One question is whether this could be related to OpLocks, but if so, would I see it always on the same table?
>>
>>I have ideas for work-arounds, but I'd prefer to figure out what's actually going on.
>>
>>Any suggestions?
>>
>>Tamar