Dave,

Couldn't I just as easily maintain that:
1) The I/O you speak of is slow by comparison;
2) It could be designed so that integrating Fox's I/O would hardly slow down the non-Fox stuff.

Were there's a will, there's a way. There's NO WILL here and we (seem) to be validating that direction.

Cheers,

JimN

>Hi Jim,
>
>>I'd bet that, sooner or later, .NET will have to grow to have data integrated into its "languages". That's why I'd like to see VFP pushed into it now *with* all of the attributes of Fox of course.
>
>Hopefully, Robert will answer also, but I'll throw in my .02 on this point. .NET already DOES have data integrated into its framework, which makes that functionality accessible to the .NET languages via the OLE-DB drivers and the data namespaces (system.data.ado and system.data.sql).
>
>Why should they add additional data functions to the languages themselves just so they can shoehorn VFP into .NET and successfully slow it down?