>>I haven't upgraded to VFP7 yet, mostly because I want to buy MSDN and don't want to double purchase. I am waiting on buying MSDN until I have my table cleared enough to try some .NET stuff out and I am also having trouble deciding on professional vs. enterprise. (It would also be cool if MSDN was about 1/2 its current price for small shop developers -- sort of like the academic pricing).
>
>If you have VFP 6.0 or VFP 7.0, you can obtain MSDN Professional at the upgrade price which is not much more than the cost of VFP 7.0 full product stand-alone.
>
>>I realize that MS probaly wants us all to move to .NET, but I also see a few more years of VFP being a valuable tool. Anyway, thanks for a great product and I am looking forward to upgrading to vfp7 and then 8 and beyond.
>
>You don't need to use the word "move". We are promoting the use of VS .NET "with" VFP, especially using ASP.NET with VFP. There is no reason to stop using VFP if it works great for you, it is a graet product. VS .NET adds many new capabilties to software development when added with VFP solutions. VFP 8.0 is going to work even better than VFP 7.0 with VS .NET and SQL Server, along with many new features developers have requested from the wish list.


Hey Ken,

Quick question...I was going over the certification criteria for MCSD.Net and VFP is not used as an elective as I beleive it was with the previous MCSD. I was wondering what the thoughts were on this if VFP can and does work well with .net, why can't we use it as an elective.

Pat.