>>Isn't that sweet?... in the VFP forum, no less!
>
>>What gave you the urge to share this?... In such a friendly way??????
>
>Not trying to be rude, just honest. I have used VFP a ton and have many apps in production with it, not bashing it at all or its fans. I am just saying it isn't the best tool for the job anymore unless that job is creating a .dbf file.

VFP shines when yo extensive data, whether that is with local or remote data. .NET missed the message when it was released for the first time. The fact that each new version adds more features to handle data more efficiently only proves this assesment.

Anyone who never did use VFP for its strenght and used it in the VB6 way would indeed not see anything missing in .NET. However the ones who drive VFP and local data processing (not neccesarely dbf) to the edge still are waiting for a better alternative on the .net platform.