Visual FoxPro 9 works fantastically. Depending on the scope of the project, how big it is ... I would advise anyone to use VFP for up to a mid-range application (local users, over a LAN or reliable Internet connection, up to maybe 20 simultaneous users), local printing (if any), etc.

The software works. VFP isn't going to suddenly not work. It's a 32-bit app written by Microsoft -- which means it was written "properly" in the Microsoft method of software development. It is unlikely Microsoft will shoot themselves in the foot so as to abandon all 32-bit software written in the 2000s for any time soon. For example, up until Windows XP, the CodeView Debugger, written for MS-DOS and Windows 3.11 back in the early 1990s, still worked.

A company I contract to still has a handful of clients on Multi-User FoxBASE+ 2.1 apps. No, I'm not kidding. The old text-based version with @ SAY and GET. And many, many more on FoxPro for Windows 2.6. I spent this past summer writing an automated converter which took FoxPro 2.6 code, which was still actively being maintained, and ported it to VFP9 working around all VFP9 bugs for 2.6 screen (.SPR) quirks. Quite a task.

But with regards to VFP9, software doesn't suddenly stop working because the toolset is no longer supported. It will continue to work as it is. And the limitations of VFP are very well known, as are its bugs. They have workarounds, and there are lots of mature tools for enhancing the developer experience, adding on features that aren't native to VFP, etc.

I would advise sticking with VFP since they already have a VFP app base.

It really baffles me that developers would refuse to use software that works perfectly, yet is no longer supported by the company who wrote it. Especially when it's software like this, and with a track record like VFP9.


>Hi All,
>
>A large Corporate Client of mine was prepared to update a VFP 9 App until they went on Microsoft's VFP Main page: http://msdn.microsoft.com/en-us/vfoxpro/bb190225.aspx and got scared by the statement:
>
>"Note that Visual FoxPro 9.0 is the last version and was published in 2007. For a great solution for building modern business applications, take a look at LightSwitch in Visual Studio 2012"
>
>which they interpreted this as "Microsoft is telling us to use another product."
>
>So we have another case of FUD - Fear, Uncertainy Doubt..So I have to reassure them..
>
>Any articles around to make the business case for VFP?
>
>BTW, Already own the wonderful Henztenwerke Book: The Business Case for Moving (Some) Business Applications to VFP in 2013 - Highly Recommended