One simple question: Why switch if VFP can do the job?

The fact that MSFT is pushing a lot of money into convincing people that .net is the closest you can get to heaven, does not make .net a better product, or VFP a worse product.

.net has a lot of features, and so do VFP. If you need features which are avaiable in .net and which are not in VFP, or whatever programming language you currently use, switch to .net. If VFP suits your need, stay with VFP.

Why follow the stream when the stream is running in the wrong direction?

>I have tried really hard over the past month to convert to windows forms C# using VS.net 2.0. Is it just me or has other noticed that the interface and apps developed in .net seem clunky and slow. The dataGridview has a very slow refresh. Also, the amount of code to connect to a sql database and all the parameters commands needed to insert, update, and delete a row in a datatable seem like more work than what’s need. I know one month isn't very long for learning a C# form base programming but I feel like I have covered a lot in the past month.
>
>After all the time I have spent understanding the numerous ways to update, insert, and delete row in a table. I find myself thinking that .net still can't touch the database development speed of FoxPro. From my view, I think .net will need about two to three more versions before it can match many of the data functionality of FoxPro. Don’t misunderstand I know that there is nothing that can not be created in .net.
>
>One last comment, .net has been around for several years now. I find it strange that most application I download from the net do not require the .net framework. (Meaning they are not written in .net) So, why do I feel like Microsoft is pushing me to switch to .net. Just allow FoxPro to compile to the .net framework. If they can make many other languages compile to it than why can FoxPro not be ported.
>
>I'm done!
>???????