If you have control over your CF Server Admin Module, you could also create a mapping to the directory, so you'd never have to worry about pathing again.
ie.
set logical pat as /includes
point to physical path c:\Inetpub\wwwroot\mysite\includes
Then in your code, anything pointing to an included file in the includes directory would just use the pathing "/includes/mycss.css"
That's an alternative.
Also with the Application framework, your CF server always calls for Application.cfm in the directory of the document being processed first. If it doesn't find an Application.cfm file there, then it goes to the parent directory and so on. That's a real hit on efficiency. So, you should really have an Application.cfm in any directory that has .cfm files, even if it is just a blank Application.cfm file (I usually put a note about me being the developer or something silly if it's my own app). So, if you really wanted to, you could path your includes in the Application.cfm relative to each directory.
That got confusing pretty quick, did you follow?
Anyway, those are two other possible solutions.
HTH,
Guy McDowell
http://guymcdowell.hopto.org
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]
