>...I was not able to simulate a problem when reexecuting the command twice. I put a maximum of 10 tries. The delay is .25 second. ... That page processes about 25 SQL commands.

If it were a desktop application, the oDataAdapter would probably be a property to reuse. Any chance of restructuring your code so that the same oDataAdapter is queried for those 25 SQL commands occuring for the single page ?

>This issue is still in progress. I hope Microsoft will address the issue asap. This is of high priority for any developer using VFP as the backend. We have to remember that this does not apply, based on my prilimary tests, on the SQLClient provider. So, even if it does not happen under .NET 1.1 doesn't mean that this is .NET and IIS related only. Because, under .NET 2.0, IIS and SQLClient environment, I was not able to simulate the problem. But, under .NET 2.0, IIS and VFPOleDb environment, I am having it.

I think you should update the bugreport (especially the headline!) to include these findings. Having components work under .Net 1.1 and failing under .Net 2.0 might be handled different from an error reported on OLEDB for vfp data<g>.

regards

thomas