>>>For what you're describing - a small mom & pop company with outdated machines - well sure I can see using it there, but they too will eventually upgrade to newer machines as they're so cheap these days so it seems you would be doing them a dis-service by giving them such an app in this day-and-age.
>
>LOL. If you come to SWFox I'll introduce you to such a mom and pop customer with a few billion $ in revenue. ;-)

Interesting. I don't consider a biz with a few billion $ a mom and pop biz - but alright perhaps their I.T. dept is tiny. Anyway I didn't say such shops don't exist - I'm just saying the numbers are quite small - small enough that it's not worth it. If they have that much money floating around I would think it would be a HUGE mistake to give them a new VFP app when you could give them a new .NET or whatever app that's ...ya know...in the mainstream.

>Not concerned about MS support. Going forward, VFP isn't a MS product- it's just a script option for the sorts of cross-platform 4GL that finally are appearing. Dr Dave tried to do it in the 1990s and then we forgot why it matters for 2 decades as one vendor basically ruled. Today? Sheesh, ZDNet surveys are 50:50 as to whether MS is winning or losing the war for developers, a result that would have been unthinkable 3 years ago.
>
>>>As far as finding developers - I assure you there are a LOT MORE C++ or C# developers avail than foxpro developers.
>
>C# yes. C++, very difficult to find- at least at a level able to manage database apps.

I assure you there are more C++ developers with database skills avail that VFP developers. Even so if that's an issue then dont use C++ use something more 'mainstream' if your concern is finding developers. Let me put it this way - if your concern is finding developers - then VFP is a HUGE no no.

>>>The language is dying so the number of developers avail drop as they're all moving their skills to other languages. Now all that being said - I can still see practical uses for VFP - like data conversions for example - but giving someone a band new desktop app written in VFP in middle of 2013? I dunno if that's such a good idea.
>
>Some would say that any sort of new desktop app in 2013 isn't such a good idea. But if you're going to do it, might as well choose something with the highest chance of being copied aboard and working first time- and whose code has a good chance of being reusable going forward, IOW it's not going to be L2S'ed or Silverlighted.