well I can't think of a good reason NOT to do it that way. Though I'm trying to hard-code as little as possible, this isn't any more than the way I was doing it which specified a path for ExpandPath.
So, do you think that maybe I should just store the image name in the DB rather than the path to it and then just implement the path in the display html, rather than in the db?
>dont make it more complicated than it has too be
>
><cfset uploads="htdocs/HHPv1/images/calendar_uploads/">
[Todays Threads]
[This Message]
[Subscription]
[Fast Unsubscribe]
[User Settings]
- path to uploaded file Daniel Kessler
- Re: path to uploaded file cf
- Re: path to uploaded file daniel kessler
- Re: path to uploaded file cf
- Re: path to uploaded file daniel kessler