Jim Dettman
jimdettman at earthlink.net
Thu Sep 22 08:30:41 CDT 2005
Charlotte (and all), There are no plans to make VFP .Net compliant simply because there is no easy way to do it. Like Access, it is a mature product, but Microsoft continues to issues new versions, the last few with significant advances and new features in the product. I've been using it off and on for 4 years now and although Access is still my tool of choice, there are things I can do with VFP that I simply can't do with Access. The OOP is growing on me, but I still feel OOP languages overly complicate things and in the end, you still end up with the same problems that you have in changing objects in a non-oop language. Over all it's not a bad product, but like any other, it does have it's faults along with the good stuff. Jim. -----Original Message----- From: accessd-bounces at databaseadvisors.com [mailto:accessd-bounces at databaseadvisors.com]On Behalf Of Charlotte Foust Sent: Wednesday, September 21, 2005 11:10 AM To: Access Developers discussion and problem solving Subject: Re: [AccessD] Access - FoxPro - SQL2000 FoxPro has been around for a very long time. It started out as a dBase clone but is based on the Rushmore database engine, which is much faster than Jet, and which is the reason Microsoft bought it in the first place. There are a lot of older apps out there that were originally written in FoxPro for the speed and then were maintained over the years rather than being rewritten in something else. Visual FoxPro eventually became the product it was supposed to be (the early Visual versions were simply a UI designer over a command line editor), but it seems to be as much a stepchild now as Access is becoming. It is no longer in Visual Studio and I haven't heard whether there are any plans to make it .Net compliant. I know Access won't be, at least not if you can believe Microsoft. Charlotte Foust -----Original Message----- From: Johncliviger at aol.com [mailto:Johncliviger at aol.com] Sent: Wednesday, September 21, 2005 1:08 AM To: accessD at databaseadvisors.com Subject: [AccessD] Access - FoxPro - SQL2000 Hi List Several time this year I've been asked to extract data a cash register type software and each ocassion the data is in Foxpro. Where does Foxpro fit into the database market? Access is generally accepted as the entry level db and SQL 2000 is for the heavy duty db. Is there are market for Foxpro skills, is it worth learning? or is it obsolete? Comments most welcome johnc -- AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com -- AccessD mailing list AccessD at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/accessd Website: http://www.databaseadvisors.com