Hi Tom,

I'm sorry, but I disagree with you. If in one hand .NET doesn't support such as a visual designer for basic class (which is not a big deal for many people, as expressed in this thread by Kevin and Bonnie), there are several other things that VFP can't even dream about and that are just trivial in .NET.

For instance, I can't tell you how many hours I've wasted in VFP work around its lack of ability to handle a form that uses some ActiveX controls in it (such as Treeview, Listview and Toolbar), generally because their events start overlapping each other, and VFP goes nuts, so I had to end up creating Timers and other workarounds like that in order to fix this. Things that in .NET I could just make use of multi-threading.

the fact of the matter is: this is the sort of discussion that we could create a *huge* list of things that VFP does better, and that .NET does better, and another list of things where they both suck, or other lists like that. :)