This does *not* appear to be a FileUpload issue because it works in Chrome
and Firefox. I'm asking this group may have seen this before and know a
workaround.

My app uses several different XML files. A user can upload the file, make
changes in their browser using of my app's forms, and save the result as a
new XML file.

If an IE user uploads a file from a Windows network shared directory, and
file download set to always require save-as, the user cannot overwrite the
file, but must rename the file or save it to a different directory. The
problem does not affect Chrome and Firefox users, nor does it affect files
opened from unshared directories.

Has anyone seen this before? Is there some setting among the gawd-awful
number of options IE gives that can change this behavior?

-- 
"Hell hath no limits, nor is circumscrib'd In one self-place; but where we
are is hell, And where hell is, there must we ever be" --Christopher
Marlowe, *Doctor Faustus* (v, 121-24)

Reply via email to