>>Hi,
>>
>>I have a VFP 9 application and ASP.NET (2.0) application, both using the same VFP database. Lately a customer has been getting frequent error 41 when updating (or retrieving) records for tables that have memo field from ASP.NET side. The ASP.NET is using OleDb provider. When they get the error they can still use the data from VFP application, no problem. And also, they could go 2 minutes later and the data is retrieved and/or updated from ASP.NET application without a problem.
>>
>>Could it be that OleDb provider senses something else but reports it as error 41?
>>
>>Any suggestions on how to deal with this would be appreciated.
>
>What TABLEVALIDATE setting you're using in your application?
On the ASP.NET (VFP Stored procedure) side it is default. I will play with different values to see if this will minimize the error. 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
