>>>>>For businesses offering solutions to vertical markets. VFP is still a viable development environment.
>>>>>
>>>>>That's hotly debatable - I have direct knowledge where vendors lost sales because their vertical market application used Fox. (In some cases, it was because the application used Fox for data storage...in other cases, even though the VFP app worked with SQL Server, the vendor still lost business).
>>>>>
>>>>>There may be factors that will improve the odds of getting a sale of a VFP app (how much or how little the app will interface with other aspects of the business) - but I can tell you with certainty that potential customers are more likely to look at the development tool for the vertical app than they were, say, 7-10 years ago.
>>>>
>>>>Yeah very debatable. I think if you had a VFP app and a .NET app that both do pretty much the same thing then I would expect businesses to want the .NET version.
>>>
>>>For instance, see the difference between a hospital system done in C#.Net and in VFP. The app done in C#.Net is 30% more expensive than the one done in VFP, but guess what, the former - which is futuristic - sold more than the latter - which is a legacy system.
>>>
>>>Click the link below to see the difference:
>>>http://www.bizboxms.com/preview
>>
>>So the C# version sold more than the VFP version?
>
>Yes. And it is being accepted by IT Managers with more enthusiasms than when we are offering the VFP version. Honestly, we need to explain to them why we are using VFP as the development tool for our product before. We need to submit links, whitepapers, etc. in order to justify why. But with C#.Net, these IT Managers are more than willing to support us just to get the contract close.

That is exactly what I would expect and what I've experienced using VFP as well. Yes you can talk them into it - but why waste the time if it's a new project? Just do it in C# and be done...