Paul McNett wrote: >> I created a framework for my n-tier solutions, and integrated >> MakeUpdatable, and it works well! >> >> My plan has been to use MySQL on the backend, so that if/when I ever >> migrate from VFP to Dabo, PHP, or whatever...there's a great chance I >> won't have to retool the backend. In fact, they can continue using the >> VFP front end on Wine (LOL!) while I create the replacement versions in >> the other dev tool. Also, it allows me to create additional add-ons in >> other tools and use them alongside of the VFP apps without issue. > > Yes, moving to a non-proprietary backend offers a ton of advantages, and > it doesn't even cost a lot if you do it at the right point in development.
Absolutely so true. If anyone out there starts a new project and wants to use MySQL as the backend, just let me know and I'll ship them a copy of the framework I used in one of my latest projects. Unless you're addicted to SET RELATION or SET SKIP or SEEK(...) in your direct tables or must have the DataEnvironment with VFP tables, you'll be able to use this (I hope) with great success....at which point, you'll probably consider staying with MySQL (or a non-DBF backend). _______________________________________________ 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.
