That's what I thought the problem would be and I get the same result when I run the code on my development machine (win2k).

I don't think 'file' is the only instance of this either. I'm sure I've seen this with a few other words as well but unfortunately I didn't note them down at the time and figured it was just me writing 'dumb' code. Maybe not...

B)

Rod Higgins wrote:
When I run the code on both our production and development servers the
cffile read creates an empty structure, even though the text file exists
and has content. I had to change the variable="file" attribute in the
cffile tag to not use the word "file". Can anyone else replicate this
problem or am I just lucky?


Hmm...

I looked at the code.. and couldn't see anything wrong with it.. and
then ran the code.. and it worked as I expected...

Did I miss something?

bye!


RH> Just came across something interesting. In cfmx 6.1 the following code
RH> will not work ... well it works but not how you would expect. Im on a
RH> windoze 2k platform.

RH> <cfif fileexists(trim(filepath))>
RH> <CFFILE ACTION="Read"
RH> FILE="#trim(filepath)#" RH> VARIABLE="file">
RH> <cfdump var="#file#">
RH> </cfif>


---
You are currently subscribed to cfaussie as: [EMAIL PROTECTED]
To unsubscribe send a blank email to [EMAIL PROTECTED]

MXDU2004 + Macromedia DevCon AsiaPac + Sydney, Australia
http://www.mxdu.com/ + 24-25 February, 2004



--
Brett Payne-Rhodes
Eaglehawk Computing
t: +61 (0)8 9371-0471
f: +61 (0)8 9371-0470
m: +61 (0)414 371 047
e: [EMAIL PROTECTED]
w: www.ehc.net.au



---
You are currently subscribed to cfaussie as: [EMAIL PROTECTED]
To unsubscribe send a blank email to [EMAIL PROTECTED]

MXDU2004 + Macromedia DevCon AsiaPac + Sydney, Australia
http://www.mxdu.com/ + 24-25 February, 2004

Reply via email to