>>>>5. VFP is data bound which makes it easier to build against databases.
>>>
>>>Not necessarily. You talk about n-tier, which throws out remote views and SPT. >You'll have to go ADO or XML. I don't think VFP provides an advantage here.
>>
>> Considering this I would say:
>>
>>5. VFP is a data manipulation language and has the local database engine, which makes the data manipulation easy (for example for the reports), after data is obtained from the (remote) data source.
>
>
>Not totally accurate. That would imply the data has to be converted to VFP cursors, which, IMO, is not always optimal. For example, if you are doing a mainly data entry/query app, ADO will work fine. No cursors needed. However, if you are crunching large amounts of data, converting to a VFP cursor may give you better results.

Agree. That's what I meant - in cases where you might need to crunch a lot of data as in my sample with reports. Another area, which is often overlooked, is some in-house data crunching which might be necessary for the project(s) (data preparation and conversion from different sources, etc.)