Hi Perry,

Even for VB.Net/SQLServer MCSD(early achiever)(you can find a few articles in UT magazine from him) is difficult to speed up dataprocessing of .Net.
We have never complain about .Net weaknesses, because they are by design. But if we develop application for customer who do not care about development tool we always use VFP.
In most of the cases we transfer all dataprocessing layer in SQLServer and refuse to use JetEngine(MDB).
A few months ago I present what is the speed diffrence in data processing between .Net and VFP because we have the same apps developed in both platforms. There is no any .Net programmer who to accept to repeat VFP2002 Tournament in its part for desktop application

HTH you in your future propositions.
Please stop to mix what is modern/heavy advertized and what is useful/productive.

>I think the real issue is programmer experience. Due to the nature of VFP, you could build a little app quickly with VFP out of the box. I think dotnet works best when you have some dll's with classlibs to make day-to-day tasks easier.
>
>i ran into an old collegue at a dotnet user group meeting Monday. He's got his own little company now. He was very pleased that he's hired a guy who build a dotnet framework using principles from Rocky Lhotta (sp?) business object philosophy. He's extremely happy with the quality of apps they are able to build.
>
>>The primary benefit of VFP (still) is the data munging and the development speed. I can knock out a well designed data crunching app in 1/3 the time it would take to do it with dotnet. Even faster when you take into consideration universal classes designed earlier that are easily transported. Part of that is the capabilities of VFP and part of that is due to programmer experience (which in time dotnet development will benefit from also). The day may come though when dotnet catches up and then it will serve both the data and the internet world won't it?