> As does everyone, I'd guess. I prefer using stored procedures for that. Once > you place your database access logic in the database itself, there's little > to be gained from saving a three-line CF file in a separate location. Unless you have to make changes to that stored procedure and now you have to find every where you called it in your code.
> And this takes me to my primary complaint about Fusebox. It tells you how to > organize your CF code. I don't think that this is where CF developers get in > trouble, generally. Instead, they should more often be thinking about how to > partition their application, and put various pieces of code in different > tiers. How about an example of what you mean then. I am interested in the best way, what ever way that may be. Right now Fusebox works very well for me. > Dave Watts, CTO, Fig Leaf Software > http://www.figleaf.com/ > voice: (202) 797-5496 > fax: (202) 797-5444 Bill K. ______________________________________________________________________ Dedicated Windows 2000 Server PIII 800 / 256 MB RAM / 40 GB HD / 20 GB MO/XFER Instant Activation · $99/Month · Free Setup http://www.pennyhost.com/redirect.cfm?adcode=coldfusiona FAQ: http://www.thenetprofits.co.uk/coldfusion/faq Archives: http://www.mail-archive.com/cf-talk@houseoffusion.com/ Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
