I'll make a short reply to Derrick's post as my posts usually seem to end up in the bit bucket. I like commenting, and CFC's, and I feel strongly about defining what the objects are in the application and THEN building the DB and components. I vote for MVC every chance I get, but.... Code is not art. This is about money and what is best for the business owner. Some apps must be highly structured. Other, smaller applications, should probably be built using procedural code. It depends on needed scalability and how much maintenance is anticipated, how much money can be spent up front etc. We all tend to code at our comfort level (and comment at our comfort level also - if at all - grrrr). Some of us get religious about certain coding principles and cut off the heads of those that disagree. What we all need to do is strive to clearly communicate the options to the business owner and then build what creates the most value for him or her. That means we should be comfortable and competent at all levels including the use of frameworks I suppose which I have little experience with. Shane Heasley CTek-Media.com
------------------------------------------------------------- To unsubscribe from this list, manage your profile @ http://www.acfug.org?fa=login.edituserform For more info, see http://www.acfug.org/mailinglists Archive @ http://www.mail-archive.com/discussion%40acfug.org/ List hosted by http://www.fusionlink.com -------------------------------------------------------------
