>>Hi,
>>
>>I have a customer that - once in a while- gets error "111 - Cannot update the cursor TableName, since it is read-only".
>>
>>The error comes from a VFP stored procedure that adds a record to the table. The procedure/function is called from ASP.NET application via OleDb provider. The table is not read-only as it work most of the times. But once in a while a user would get this error. Is it possible that OleDb provider reports the wrong error number, since I suspect that it is something different?
>>
>>Any other suggestion, I would appreciate it.
>
>Is it under high stress when you get the message? I've seen anti-virus software cause this when opening and closing a lot of tables where the anti-virus wasn't done scanning the table when we wanted to write to it. We usually turn off scanning DBF, FPT, CDS from the anti-virus.
I was actually thinking about anti-virus software too. I will ask the network admin to disable it or at least to find out if they do run av software. Thank you.
"The creative process is nothing but a series of crises." Isaac Bashevis Singer
"My experience is that as soon as people are old enough to know better, they don't know anything at all." Oscar Wilde
"If a nation values anything more than freedom, it will lose its freedom; and the irony of it is that if it is comfort or money that it values more, it will lose that too." W.Somerset Maugham
