Steve Onnis wrote:
I can can include "C:\xxx\yyy", then it does not matter
where I call it from, I know the path will always be right rather than having
to try and work out where I am to get to the file I
need to get to and do a relative path include.
But why do a relative path include at all? Why not just use
cfinclude/cfmodule with absolute mappings (i.e. starting with a "/")?
I think the only place I've ever used a relative include is in an
application.cfm to load the application.cfm in the parent directory.
Every other time I use an absolute mapping, using expandPath if I need
an actual file path. Perhaps if you explained what the file is you're
trying to work with and its relationship to the file you're trying to
derive the path from we could help more.
Cheers,
Robin
http://www.rocketboots.com.au
---
You are currently subscribed to cfaussie as: [email protected]
To unsubscribe send a blank email to [EMAIL PROTECTED]
Aussie Macromedia Developers: http://lists.daemon.com.au/
