Mike, It can be referenced fine from within the CFC, but it's probably not a good idea. A CFC shouldn't "reach out" to external data, but instead be told what it needs to know. Doing otherwise breaks what's known as 'encapsulation' in the OOP world. Basically, it lowers the reusability of your CFC: what if you were migrating between two databases, your CFC had a perfect method to talk to both, and you wanted to instantiate two instances pointed at two different datasources?
Cheers, Joe On Sat, 30 Oct 2004 06:15:21 -0400, Mike Alberts <[EMAIL PROTECTED]> wrote: > Ok, I must be missing something here, but I specify my datasource in my > Application.cfm file (in the request scope, framework was written in CF5 days) and I > can reference it just fine in a cfc as #Request.Datasource#. > > Mike > > > well here is the reason why i ask > > (raymond hasnt blogged about using the ini method yet) > > > > i was thinking that since u cant call some variables such as your > > datasourse names outta your Application.cfm file, that you could just > > include them, so u didnt have to (lazily) manually change them. > > > > > > know what i mean? > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Purchase from House of Fusion, a Macromedia Authorized Affiliate and support the CF community. http://www.houseoffusion.com/banners/view.cfm?bannerid=38 Message: http://www.houseoffusion.com/lists.cfm/link=i:4:182997 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/4 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:4 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.4 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
