This might spark a whole debate here but, I personally like to call <cfmodule> in place of includes when even possible. I feel it's a more semantic way of getting things done where you know exactly what is getting dragged into the module vs. an include which may use any of the variables used above. A module needs to know what to expect.
you can still run your modules for headers, footers, row headers but at least you know what it's doing when it's running. An include can do anything... you don't know what to expect until you open it and inspect it. Casey ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| ColdFusion 8 - Build next generation apps today, with easy PDF and Ajax features - download now http://download.macromedia.com/pub/labs/coldfusion/cf8_beta_whatsnew_052907.pdf Archive: http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:293344 Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
