Essentially that is what I have, I like having a full CFC for each db instance instead of including the SQL. Thanks for your replies.
Bryan -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jim Davis Sent: Thursday, January 15, 2004 5:55 PM To: [EMAIL PROTECTED] Subject: RE: [CFCDev] Making sure is not called out of sequence I agree - but don't see much else to do. As an aside I've taken to maintaining a "broker" component that calls DB Code from a different set of CFIncludes in sub folders. Each sub folder contains ONLY the DB-Specific code for each supported DB (or storage mechanism since you're limited to DBs) but the object-model is maintained as since the broker provides a standardized interface. So far it's working out very well for me - and has reduced a lot of redundancy. Jim Davis ---------------------------------------------------------- You are subscribed to cfcdev. To unsubscribe, send an email to [EMAIL PROTECTED] with the words 'unsubscribe cfcdev' in the message of the email. CFCDev is run by CFCZone (www.cfczone.org) and supported by Mindtool, Corporation (www.mindtool.com). An archive of the CFCDev list is available at www.mail-archive.com/[EMAIL PROTECTED]
