Well a good survey would be how many developers who are actively still selling .vfp. apps have dropped .vfp. totally and rewritten everything in .NET. Doing this is difficult, expensive, and time consuming and I disagree with your assertion that everyone is doing this. It just wouldn't be common sense...
>>
>I will probably get to this sometime for point by point analysis, but, just not having to rewrite thousands of lines of vfp into a totally new language is sort of obvious for starters...
>>
>
>If there is any sense to bolting Fox to a web service - leveraging existing functionality is it - I agree 100%. Nonetheless, you are talking about an extremely small % of Fox developers who will do this in a production setting.
>Granted - the evidence is anecdotal - but there is nothing out there to refute it. Whenever a discussion occurs here about who is actively doing this sort of work - you don't get much in the way of a response.
>
>With that in mind - you can begin to understand why web services in Fox does not have broad appeal and therefore - will not be of interest to Fox magazines who must aim at the heart of the bell curve - the mainstream Fox developer who writes relatively mono-lithic apps to local data.
>
>< JVP >