VFP, IMO, is an all-in-one product meaning it can do pretty much everything without the need for alot of extra products. Unfortunately, this sort of product doesn't generate as much revenue as VB+Access.OR.NET+SQL+ all the other tie-ins that the other products generate. Therefore, IMO, MS does not market it out of fear it will eat into the other areas.
The reality is that you can do just about everything with vfp that you can do with .NET. This includes web programming. You can even have a .NET web site that, in reality, is pure vfp code - see: http://www.activevfp.com/avfpdemo2/default.aspx
>Hi all
>
>Why VFP cannot be VFP.NET ?
>
>1.Because of the DBF ?
> -> IMO. Kill DBF use sql server
>2.Not many programmers know how to write VFP ?
> -> Where can i find a website that I can post "I use VFP"
>3.Is VFP sales not even in the top 10 or top 20
> -> Kill all pirated VFP copy ...see 1 report to Microsoft :) (Same as movie nowdays )
>4.Because VFP can be decompiled
> -> For me i dont care, i think is faster to write than to understand people source code (more challenging, learn more )