>><snip>
>>
>>>I write software for retailers... and in our world, we know the most dangerous customer is not the one who complains - it's the one who quietly just goes elsewhere. I worry that that is the future of many current VFP developers.
>>
>>If I understand correctly you write applications for a vertical market?
>>
>>Why would making it with VFP make a difference. Unless there are things that can't be done and .Net is the solution.
>>
>>I'm wondering because I'm working on a vertical market application and the use OF VFP has no importance (yet). What is important is that the application is working like it's supposed to work and the price is right.
>
>Hiring other developers, a decent # of my clients do care what the app is developed in, we use a SQL based backend (either MSDE or SQL Server) so with the next version of SQL Server, guess what, it's .NET based (of course the t-sql will still run), but the backend being .NET/CLR based will give more of an incentive to learning more and more about .NET. Not a biggie, accepting change is an important part of the development world, I'm just at that point that I'm realizing I need to say goodbye to my long time pal, VFP. I'm going kicking and screaming of course and I've been thinking it for about a year and a half now, but the MS position of not marketing, not complaining, no changes, dying on the vine is what has helped propel me to make that change.

What you said makes a lot of sense for your business. I can still live with the fox for a while.

But because MS does'nt seem to like VFP as much as we do it'll be harder and harder to ignore .Net
>
>But, you're right that VFP is not only not that bad, I think it still kicks butt..