I don't know what others would say but we've found it useful to put all the queries, server-side form validation, and business logic in one or more cfcs. Then the "action" page just acts a controller, taking in the action that was requested and calling the appropriate function(s) in the cfc to perform it, passing along the parameters submitted in the form. This way, the cfc can be reused generically to interface with the database (for example, with Flash Remoting). The other pages you describe would also call functions from the cfc--SELECT statements to pull stuff out of the database for display.
dave --- David Tobey Par Avance, Inc., www.paravance.com (303) 447-0878 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Archives: http://www.houseoffusion.com/cf_lists/index.cfm?forumid=4 Subscription: http://www.houseoffusion.com/cf_lists/index.cfm?method=subscribe&forumid=4 FAQ: http://www.thenetprofits.co.uk/coldfusion/faq Structure your ColdFusion code with Fusebox. Get the official book at http://www.fusionauthority.com/bkinfo.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
