Maybe you're right - but does it matter?:-)

>I bet the only .net people using VFP Comm objects as a middle tier are some VFP programmer's. Look at the main .net support sites like code project, or dotnet nuke etc. None of them have any articles or software based on VFP Comm objects.
>
>
>>>Maybe I missed the boat on .net, but I don't use the vfptoolkit for .net nor do i use vfp tables. Most production apps that are in .net use mssql or oracle or somesuch. Would you care to quanitify your statement with some kind of facts?
>>
>>The presentations I've seen rely on VFP COM to parse data in and out of XML, and ADO, so that a cursor, with a record pointer (VFP Cursor) is available for the VFP COM to quick-crunch the data set, and the parse back to a format the other ties can work with. Somtimes a reiterative cursor - with a record pointer is better than slogging through whatever other sources and structures the architecture may require.
>>
>>The reason : VFP is still the fastest data engine on the market! Not all applications just serve lists to a browser - some still have to crunch numbers and cross reference data in other tables. Not every app is a Viagra order entry page:)
>>>
>>>
>>>
>>>>>It may be that he made the contoversy over running VFP on Linux a personal issue and has decided to cut his ties to the community. I know he's not doing anybody any favors when he says that Microsoft has replaced VFP with .NET which apparently is very far from the truth...
>>>>
>>>>Exactly! In fact - I see quite the opposite - my understanding is that VFP COM objects are essential to middle tier .NET solutions.