Hi John,

I vote for .Net with a SQL Server back-end. As much as I love Fox, I find that a properly architected .Net app and SQL Server backend can approach it's speed. Amazingly, once you get past the syntax and staggering number of classes in .Net it's pretty easy to apply your hard-won VFP knowledge and experience on how to build a good application.

VFP won't continue forever; neither will there be an opensource version.



>Hi Guys
>Decisions, decisions - this question has been asked a thousand times, but....
>The problems with Terminal Services, the anti Fox attitude among ISP's and opposition vendors (every chance is taken to tell prospective clients how bad Fox is), the push towards SQL Server all lead me to believe one must eventually think about moving on.
>Sale of a good package is (apparently) influenced by whether it has been written in flavor of the month development tools etc etc.
>The prospect scares me not so much re-learning a platform (done that before from VB to Foxpro to VFP) as the fact that anything I see written with SQL Server as a backend is abysmally slow when compared with VFP.
>So the question is:
>SQL Server (or My SQL) with a VFP front end ?
>SQL Server with a .NET front end ?
>SQL Server with a VFP front end compiled to .NET ?
>I still have FPD running on sites and running well, but they don't generate income, too stable etc
>Does this mean VFP will continue forever ?
>I have heard ramblings about an open source version? Does this mean Fox will not die?
>One thing I have noticed is that the numbers on UT are dwindling is that because all the questions have been answered or are programmers voting with their feet?
>Cheers, John