>>Like I said, I can understand WHY it has to be this way, but I do feel cheated having being made available to some brilliant DB commands in fox, only to have to be brought back down to reality with a different product.
>
>Kevin,
>
>VFP has a native database engine, VB does not. Simple as that. So it's not truly an apples-to-apples comparison.

Yes, I understand that, and if that's the case, maybe Visual Studio .Net shouldnt' be marked as being brilliant for DB apps, when it clearly isn't in terms of performance. I know it will improve over time, but never to the standard VFPers are used to.

>
>Just out of curiosity, have you tried the same operations in VB.NET using the ODBC driver instead of the VFP OLEDB provider? It might perform quicker.

No, I haven't tried it, I was under the impression the OLE DB provider is quicker.

Kev