I've actually found that globals is not that good an idea as it makes maintenance a pain.
If you do require includes from another fuse, then work the path out and include (../security/queries/qry_member_details_select.cfm) BUT There is no hard and fast rule. What I would say is that if your fuse requires functions from another fuse, then you should maybe consider them to be sub fuses and not seperate independent fuses. The other option is to copy the files into the fuse. At least you'll know the code will work exactly as planned within that fuse and any changes to the other fuse will not impact other fuses. Adam > -----Original Message----- > From: Ellwood [mailto:[EMAIL PROTECTED] > Sent: 24 October 2003 10:25 > To: [EMAIL PROTECTED] > Subject: RE: [ cf-dev ] Any fusecoders on the list? > > > True, I hadn't thought of that. If I wish to drag my circuit to another > application then it will fail because of the globals being missing. > > This is why I asked the question in the first place. Thanks for your > valuable input I will rethink my strategy. Although I am > currently wondering > if there will ever be a perfect solution or just a best compromise. > > Regards > > Ellis > -- ** Archive: http://www.mail-archive.com/dev%40lists.cfdeveloper.co.uk/ To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] For human help, e-mail: [EMAIL PROTECTED]
