Skip to main content

Whither VFP? Umm...still right here...

Had an interestingly brief conversation with an MTI (http://www.mtihorizon.com) customer yesterday about Visual FoxPro. They hadn't loaded in the new version of Horizon yet (which is now under VFP 8) and were still running VFP 6 or 7. "Is VFP still around? Didn't MS stop supporting it?"
 
Response: Of course it is. MS has it on its "what we support chart" until 2010 or 2012. They are hard at work on a new version. The product continues to grow and evolve. Yes, it's an older product. Not much products make it past 5 or 6 versions. That says a lot for FoxPro and its team.
 
Question: Why did QUALCOMM switch over to SQL Server?
 
Well, their actual application was still done in FoxPro, for one. (they now offer a web-based version, which obviously doesn't use VFP but it isn't quite as smooth as it could be). But they had grown from having a handful of customers accessing data and wanted to provide a larger centralized database. Enter SQL Server.
 
Sure it's easier to find SQL Server DBAs these days - they're falling off the trees. And VFP's own database strategy has been hurt by all those times when power surges corrupt memo fields, etc. You can't always change bad impressions people get. So is SQL Server the only answer? Of course not, in fact, at one of my other clients, we came across a situation where a typical SQL DELETE completely ruined their database (thank goodness for backups, not DBAs in that case). Put a VFP View in to access the same data and bang! same SQL DELETE - didn't wipe out their data.
 
Herein, I think, lies VFP's biggest challenge. And it always has been. The perception that it is simply a database while its strengths lie in doing so many other things, such as accessing data, building apps, etc. Jim Duffy, I think, does a great job of illustrating this in conferences. He stands up and bashes VFP as a database while promoting SQL Server and MSDE left right and center. But he STILL works with VFP as a tool.
 
How do you switch perception? WIth a product that's almost 9, it's tough, maybe even impossible. But that doesn't stop the people who can make it fly from doing so.

Comments

Popular posts from this blog

Blogs and RSS come to Microsoft.com

MS has just introduced their portal and it's pretty comprehensive. Nothing quite like learning that some people use AIM instead of MSN messenger, or that there really may be a need for supporting 4 monitors ( Cyrus Complains ) However, it's really a great sign that MS is serious about supporting the blogging community which seems to have um, exploded in size in the past year. Blogs and RSS come to Microsoft.com

Elevating Project Specifications with Three Insightful ChatGPT Prompts

For developers and testers, ChatGPT, the freely accessible tool from OpenAI, is game-changing. If you want to learn a new programming language, ask for samples or have it convert your existing code. This can be done in Visual Studio Code (using GitHub CoPilot) or directly in the ChatGPT app or web site.  If you’re a tester, ChatGPT can write a test spec or actual test code (if you use Jest or Cypress) based on existing code, copied and pasted into the input area. But ChatGPT can be of huge value for analysts (whether system or business) who need to validate their needs. There’s often a disconnect between developers and analysts. Analysts complain that developers don’t build what they asked for or ask too many questions. Developers complain that analysts haven’t thought of obvious things. In these situations, ChatGPT can be a great intermediary. At its worst, it forces you to think about and then discount obvious issues. At best, it clarifies the needs into documented requirements. ...

Programmers vs. Developers vs. Architects

I received an email this morning from Brandon Savage 's newsletter. Brandon's a PHP guru (works at Mozilla) but his newsletter and books have some great overall perspectives for developers of all languages. However, this last one (What's the difference between developers and architects?) kind of rubs me the wrong way. Either that, or I've just missed the natural inflation of job descriptions. (maybe, it's like the change in terminology between Garbage man and Waste Engineer or Secretary and Office Administrator) So maybe it's just me - but I think there's still a big difference between Programmer, Developer and then of course, architect. The key thing here is that every role has a different perspective and every one of those perspectives has value. The original MSF create roles like Product Manager, Program Manager, Developer, Tester, etc - so every concept may pigeon hole people into different roles. But the statements Brandon makes are often distinction...