Michael, > I respectfully disagree, if you've designed your application > in a N-tier fashion so as to not bind your hands by building tons of that > "complexity" into your application. > > I've been using a N-tier approach for 5+ years now and it makes my > development life very easy, especially since I've got my own little > framework that is well suited for my tasks.
I wouldn't argue in the face of your accomplishment that it *can't* be done. Certainly for every rule there are exceptions. Look at some of the amazing stories of people who scaled Mt Everest by themselves, one with only 1 leg, another without oxygen. My case is directed more for the "average" (which I consider myself) VFP developer, who first wants to do what he/she loves to do - but also desires to stay independent by not getting sucked into a "vortex" of growth and into the vastly more competitive, expensive, and I believe arguably more complex, world of C/S applications. Again, granted there are some people who can do anything. Considering complexity, as we know there are multiple choices when it comes to backend DBMS's. In fact, those of us who have daubled with just MySQL have to deal with differences between versions, not to mention distribution and maintenance difficulties. And then there is the matter of following ongoing progress in the C/S world with an lookout for the Next Big Thing to jump to. In a big way, I'm happy that MS stopped mucking with VFP. While I have nothing but respect for the VFP dev team, MS's "out with the old, in with the new" philosophy would have pushed them in the direction of changing existing features instead of adding to and extending the product. I've had my fill of MS in this regard. We can work with VFP9 as it is well into the foreseeable future, and I like not having to worry about what MS is going to do next. The main reason it's taken me forever to "shrink wrap" my products (I have 2 now) is that I believe all the I's have to be dotted and everything has to be secure, well tested and documented. I'm working with a small customer base until all of this is done, and then expect to "mass deploy" to hundreds, hopefully thousands, of users. I believe that had I switched to C/S centric, the added cost/complexities would have delayed these projects and kept me on a treadmill. Having said this, I should add that I do have a few features that employ MySQL, but (1) they are optional add-ons to the self-contained products, and (2) utilize a MySQL installation on an inet server that I manage, versus requiring the customer to be involved in any way with this activity. Lastly, as we've discussed off-line, marketing is a really big - and very expensive - deal. Put all this together and if you can deal with all this without missing a beat - or compromising your independence - then all the more power to you! :) Bill > --Michael _______________________________________________ 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.
