cfimport and cfmodule have the same problem. You can't use variables in the location attributes. I was told that cfimport has been scheduled to be fixed. Don't know about cfmodule.
I don't agree with having to hard code any values in anything, but that was MM choice and it indeed sucks.
Why can't you use a relative path in your cfmodule?
Bryan, I'm not sure if the "fix" you heard about for cfimport is really coming. Based on the implementation of cfimport, it's simply not possible to use variables because cfimport is a compile-time directive, not a run-time directive. Therefore, the compiler needs to know the path to import up front. That, together with Macromedia's mantra of backwards compatibility, makes it a bit suspicious to me that they'd fix it in such a way that the implementation completely changes.
Regards, Dave.
----------------------------------------------------------
You are subscribed to cfcdev. To unsubscribe, send an email
to [EMAIL PROTECTED] with the words 'unsubscribe cfcdev' in the message of the email.
CFCDev is run by CFCZone (www.cfczone.org) and supported by Mindtool, Corporation (www.mindtool.com).
An archive of the CFCDev list is available at www.mail-archive.com/[EMAIL PROTECTED]
