>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.

Michel Fournier, this site's owner ran into problems accessing VFP tables via the OLEDB provider, under stress. My understanding is he spent a *lot* of time with MS on the issue, which was never resolved and was one reason he switched the UT to a SQL Server backend.

IIRC he was getting several different errors intermittently, I don't know if 111 was one of them.

You could search messages from Michel about VFPOLEDB. I think some of them were between Michel and I, that issue interested me.