I think your running into the IIS 'feature' that locks files for you. This
'feature' can be disabled, and someone on this list had a good way of
handling it. You should be able to find it in the archives.

=======================================================================
Raymond Camden, Principal Spectra Compliance Engineer for Allaire

Email   : [EMAIL PROTECTED]
ICQ UIN : 3679482

"My ally is the Force, and a powerful ally it is." - Yoda

> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, January 09, 2001 11:53 AM
> To: CF-Talk
> Subject: CFFILE Delete then WRITE issue....
>
>
>
> OK.  I am having a problem here.  I am able to DELETE a file with CFFILE
> without a problem, but when I try to almost immediately WRITE the
> same file
> back it tells me there is an issue with the file "Error: The file
> could not
> be accessed."  Has anyone encountered this before?  When I check on the
> server for the file, what once was a 500k file, is now only 500 bytes, but
> when I try to open it there it tells me that the "file could not
> be found."
> But it exists.  And then I have to wait a while to get the OS to release
> it.  I check it 24 hours later (because I am working on other things too,
> and I so sleep some), and it works fine.  I think this is an issue if
> someone tries to OPEN the file instead of SAVING it.  So the second
> question is is there a way to force someone to DOWNLOAD the file
> instead of
> opening it?
>
> Also, when I browse that directory in CF Studio, the file name has a RED
> DOT to the left, and I have never seen this before.
>
> Any help would be MOST appreciated.
>
> Vance Duke
> Cold Fusion Application Developer
> i2 Technologies
> (469) 357-4729
>
>
>
>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Structure your ColdFusion code with Fusebox. Get the official book at 
http://www.fusionauthority.com/bkinfo.cfm

Archives: http://www.mail-archive.com/[email protected]/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists

Reply via email to