In the last year, we have discussed a lot about the VFPOleDb bug when being used under the .NET environment for Web site. Basically, this data provider, when being used in such environment under IIS, creates a lot of weird behaviors. We have seen a lot of workarounds and things like that. When we moved to SQL Server, this has disappeared completely. The SQLClient which is native to .NET, is way ahead in regards to that. But, there is also something more that disappeared and this is what I want to discuss here.

When in such environment, we have faced error messages like this:

Unable to read beyond the end of the stream.
Invalid length for a Base-64 char array.

As suprisingly as it gets, after 20 days under SQL Server, we never have seen those errors either. So, basically, the fact that the VFP data provider was corrupting a lot of stuff in memory was creating a lot of other related errors such as those two mentioned.

At first, I have been trying to find what was causing this. I was sure this was caused by something else. But, to my big surprise, it all seems to be related to teh VFP data provider. So, this is another big thing resolved.