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

Merry Christmas

Whether you celebrate now, have already celebrated your past holiday, are planning to, or not, I hope you find yourself surrounded by family and those you love during this holiday season and are able to remember fondly those who are not with you. We often find ourselves buried in work, or too distracted by other problems, to share and remember a few moments with those closest to us. So many of us are separated by huge distances, we often find it easier to focus on those who are out of arm's reach yet so easy to connect with online, instead of those who are right beside us. So do yourself a favour, put down the keyboard (stylus, mouse, etc) and spend that time. I know I will. Merry Christmas. Powered by ScribeFire .

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...

From Writing to AI: the pattern repeats itself

When I was ten years old, my dad bought a computer and, thanks to an advertising supplement in a Superman comic I read, it was a TRS-80. A month later, he dragged the entire family (my mom and brother were not the most enthusiastic) to a class at Radio Shack teaching how to use microcomputers. At the time, I understood why my mom wasn’t that excited: the computer was yet another gadget in the house. But today I find it fascinating. My mother went to Vassar in the 50s. She learned how to type — not a common skill at the time — but it opened doors. Her ability to communicate effectively led her to a career in adult education and later communications work with the CBC (Canadian Broadcasting Corporation). This isn’t a nostalgia post. Today, the ability to use artificial intelligence, be it through Copilot or simply writing the right prompt, is becoming a critical skill. But is it really that novel? In the 1500s and 1600s, the printing press gradually made reading accessible beyond cler...