On Jun 28, 2006, at 3:12 PM, David Crooks wrote:
Right, VFP9 is just an illusion and the fact that MSFT will support it until 2015 is a lie.
That's irrelevant from the POV of a company. There was nothing wrong with VFP 7 or 8, so releasing 9 doesn't suddenly make it a viable product. And Microsoft's "support" also means squat. How many times has Microsoft saved the day by "supporting" VFP?
Microsoft stopped promoting VFP as a solution years ago, and the fact that such a powerful tool is virtually unknown outside of our community is a direct result of that. I've spoken to Microsoft reps as far back as 2000 who didn't know that they still owned VFP, much less still sold it. I doubt you could find a single rep who wouldn't be able to answer that about Visual Studio or Word.
VFP isn't going to stop working, even after Microsoft stops supporting it in 2015. Apps written a decade ago will still work a decade from now. That's not the point, though. The point is whether it is wise to recommend *new* development be done in VFP in companies that are not already full of VFP developers. As a consultant, I haven't been able to recommend that for years now.
-- Ed Leafe -- http://leafe.com -- http://dabodev.com _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/profox OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
