>> what can you do in VFP that you cannot do in .NET today?
>
>I don't think there is an equivalent to the builder technology that VFP has. A particularly tedious situation is to create a datagrid and populate the appropriate properties there, at least in the demonstrations/articles I've been exposed to.
>

You can create properties builders in .Net. I haven't done it, but it can be done. You can also create property editors... which VFP is just supposed to be getting in 9.0.

>I haven't seen the ability to create a "quick report" like I can do in VFP.

You are correct that there is no reporting system built into VS. But, if you are using Crystal you can do this. Also, sql reporting services has a quick report wizard.

>These are off the top of my head. Those with more experience with both perhaps should be able to come up with more.

I can come up with just as many the other way. Multi-threading, Structs, Constants, Enums, Properties (real ones not the access/assign look alikes). Of course, we won't even talk about web development which VFP doesn't even try to support out of the box unless you want to build com servers to use with ASP pages, which of course has been done and will work, but it is pretty slow and brittle.

Heck, I love VFP too... but, just cause it is good and .Net does a few things differently doesn't mean .Net is not any good.

BOb