>>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?
Regards. Al
"Violence is the last refuge of the incompetent." -- Isaac Asimov
"Never let your sense of morals prevent you from doing what is right." -- Isaac Asimov
Neither a despot, nor a doormat, be
Every app wants to be a database app when it grows up
