So, basically, if I don't want to rethink and rebuild my whole development environment, I should stick with good 'ol Application.CFM? There you could simply do <cfinclude template="../Application.cfm">.
It seems indeed that "you can't" is the answer here, but shouldn't it be possible to do that? Is there a good reason for not having relative path support (and I mean "../", Will) for extending components? In this objective, Application.cfc is a step back from Application.cfm. Can Adobe shed some light here? I know you're reading this ;o) Wim. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Adobe® ColdFusion® 8 software 8 is the most important and dramatic release to date Get the Free Trial http://ad.doubleclick.net/clk;192386516;25150098;k Archive: http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:307407 Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
