>>>So, in other words, in your experience, the VFPOLEDB provider is not mission-critical reliable?
>>
>>At the data level, we have implemented workarounds. So, we never missed a transaction.
>>
>>The move to the SQLClient data provider, because it is native to .NET, moved it to 2.5 times faster for every database hit.
>>
>>The two errors mentioned in the other message were unavoidable. So, when the happened, that caused an error to the user.
>>
>>And, of course, the move to SQL Server opened a bunch of brand new doors such as the ability to index at real time and stuff like that.
>
>Do you think you could summarize your experiences with the VFPOLEDB provider, and the workarounds you did to achieve reliability? It would be a useful public service.
>
>Or, is it proprietary?

I second that. Using your experience I advised against even trying to use VFP data for ASP.NET application we discussed yesterday with my colleague.