>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 is not an issue. The test page was only using one and it was the same result. IAC, the data provider need to be independent per SQL as many of those SQL properties and methods are being accessed while others are being processed. There is about 20 methods and 20 properties of the data class and one SQL is generally bound to once instance of the data provider object.

>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>.

I was not aware we could update the entry once uploaded. I will check on that.