>>
There are many complex loops of code execution you can do in VFP that runs faster than .NET (C#/VB) code, while there are many things you can do in .NET that run faster than VFP.
>>

Text being one of the things .NET seems to handle - hands down - faster in .NET.

The issue as I see it is that the VFP OLE-DB Provider is a separate entity - which apparently has advantages not found in the classic Fox interface. Again, as I said, this would not surprise me.

The other issue is that what is really attributable to the 4 second difference. Is it soley due to the Fox OLE-DB Provider. OR, is it also in part due to .NET being the client?

In the end, it really does not matter because anyway you slice it, native fox - working with native data - GOT BEAT by .NET using the VFP OLE/DB Provider. Is it scientific? No...but again, I am not sure it matters.

FWIW, I think Houston was more interested in you saying Kevin and I were wrong in our theory....< bg >.....

Once, text was the holy grail, and .NET proved to be faster than Fox. Now, could it be that native data access is the next thing to go???

You know....somebody, some people will realize that .NET is a good performer...