>>
>That would be really surprising, and I don't think it is true! Optimizations, if any, used by OLE-DB would have been incorporated into VFP by now.
>>
>
>I don't think you can say this so matter of factly...

Of course I can't! It's only speculation; isn't that what we're doing here?

>And, it may be that the same optimzations are in place, but the native VFP environment has over-head the ole-db provider is not burdened with.

Yet any overhead that may exist in VFP runtime vs its OLE DB provider should not be that significant. After all the system requirements for running either are the same. Anyway, I really consider it a non-issue at this point.

>
>Regardless of where the problem rests, .NET+VFP OLE-DB Provider looks to be as good or better than pure Fox and native data.

I wouldn't jump to that conclusion just yet. The VFP code posted by Kevin can be optimized and it's only up to Kevin to do it. Until then the test results are irrelevant. Nonetheless, the data test queries from .NET are impressive.. after all they're using VFP technology :-)