So right away we lose one big feature of VFP, just so we can get to a "common denominator"???

Hardly has the ring of "fairness" to me.
Can you explain how a shortcoming of one platform has to be catered to in the other platform?



>I agree. You should use SQL Server as it compares apples to apples.
>
>>VFP and .NET Data Comparison
>>OK here we go... First lets establish some base stuff.
>>
>>What are the unique characteristics of each technologies data access methods ?
>>
>>VFP
>>Can open DBF files locally.
>>Can access data via ODBC and OLEDB
>>Data is maintained in global memory space
>>Has a unique DML Syntax
>> REPLACE ALL
>> DELETE FOR
>> UPDATE/INSERT
>> SELECT
>> SCAN FOR
>>
>>
>>.NET
>>All data is considered remote data
>>Can access data via ODBC, OLEDB and native .net data providers
>>Data is maintained in memory via objects
>>All data access is done via object/property syntax.
>>Future tech LINQ has capabilities similar to the SELECT statement in VFP.
>>
>>This is the start of my list. Contributions to the list would be appreciated…
>>
>>I would like to focus our discussion on accessing data from SQL Server. Each platform does a good job of retrieving data from SQL. While the .DBF does have its benefits I think we should focus on how it behaves in a client/server/distributed world. Sound good?
>>
>>
>>Rodman