> Where I work now, it is VFP7 which was released 6 years ago and does the > job.
I still compile in VFP7, mostly to avoid taking my clients through an uninstall/reinstall just to get the VFP9 run-time files properly registered, and laziness in not designing a way to do that with a routine update in the exe/app files. I code in VPF9, using SET ENGINEBEHAVIOR 70, just because I like the editor more. VFP7 is plenty punchy for my needs, and quite stable. Gil > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] Behalf Of David Crooks > Sent: Tuesday, April 03, 2007 2:13 PM > To: [EMAIL PROTECTED] > Subject: RE: Another life after VFP thread? > > > On Tuesday, April 03, 2007 1:48 PM Ed Leafe wrote: > > > That's pretty clear, IMO. Microsoft will not do anything to > ensure that it will continue to work; if it > >does, well, that's just dandy. > > > Sounds like a "bet the company" strategy to me! > > It has Always been that way with FoxPro/Xbase. Many people left Fox to > Delphi and others and look where it got them. As long as the tools I > use to develop database applications work then it is not a problem. > Where I work now, it is VFP7 which was released 6 years ago and does the > job. > > David L. Crooks > > > [excessive quoting removed by server] _______________________________________________ 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 Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/[EMAIL PROTECTED] ** 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.
