Michel,

Have you considered just giving up on the VFP driver and going to SQL?

If you plan on having a high volume application like this, the VFP OleDb provider is just not the right choice. It never has been - heck it took and VFP 9 to even get a multithreaded driver and apparently that driver has issues now...

The only reason why you wouldn't use SQL Server is cost and given the time you're pouring into trying to make the VFP OleDb driver work I doubt that the cost of SQL Server is going to be an issue, especially given no matter what you do you will never be able to fully administer the data using the VFP OleDb driver entrirely (Index, Pack, etc are difficult or impossible to do especially on a live database plus the whole hell of DELETEd records in DBF files).

I realize that you think this should just work and I agree. But the driver has never worked well and I would never trust it for anything but small applications... And even then it's such a throw back compared to the integrated SQL support in VS.NET and the SQL Tools.

+++ Rick ---


>>I finally ran a NET1.1 test on IIS6 and got no errors. This was on the same web server that hosts the NET2.0 test. NET1.1 was significantly slower. On a 5 minute test:
>>NET2 38562 hits (128/sec). 252 errors.
>>NET11 20938 hits (69/sec). 0 errors.
>>
>>Also can confirm that the 'SET REPROCESS' suggestion has not effect.
>
>Thanks, I updated the page with your information:
>
>https://connect.microsoft.com/feedback/viewfeedback.aspx?FeedbackID=217718&wa=wsignin1.0&siteid=210