>>>>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.
>>>
>>>Can your SP do some logging of the errors either into textfile (which is AFAIK, not allowed) or to another table in case of errors?
>>
>>I believe I can log the error but not sure what it will accomplish. I already know the error. Thank you.
>
>I meant here that you can log all other relevant info, such as user name, the table name, etc.
I already know all these information from the error message. I will investigate turning off the anti-virus software on VFP tables, as suggested by Chuck Mautz. This could be the solution (hopefully) of the problem.
"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
