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

I do remember reading some of his (MF) messages on the problems with VFPOLEDB. And I will search for those messages. And I am already talking to the customer IT to see if they could exclude my application files from the AV checks. This is the easiest steps (as far as I can see) to try.

As to switching to SQL Server backup. This is my very important goal this year to convert my app to SQL Server. I can't stand dealing with VFP corruptions and other issues any more. I am actually working - every day - changing parts of my application by moving the data calls from being monolithic (in methods and functions of the program) - to DA layer/tier where the data access can be done either to VFP or SQL Server. In every new update my customer gets some features are changed to using my new SQL Server/VFP approach. So my customers are my alpha and beta testers on the go <g>.