«

Bob Barrows wrote:
> Neil Gould wrote:
>>>> Here is another repro using clsupload. Exactly what do I have to
>>>> disable in my browser to make this stop working?
>>>>
>>>> <%@ Language=VBScript %>
>>>> <!--#INCLUDE FILE="clsupload.asp"-->
>>>>
>> In comparing this variant with the one currently in use (that creates
>> a BLOB object), one functional difference aside from the ActiveX
>> issue is that the ASP processing code in this one doesn't work if
>> separated from the form. For example, having a form action =
>> "someASPfile" that uses the above ASP code and includes clsupload.asp
>> results in the process failing due to the "object" being closed.
>>
> This does not sound good either. I have several pages working that
> use this approach (a file-processing page that handles requests from
> several form pages). Could you show me exactly what I have to do in
> this ASP code to reproduce your symptoms? Here it is again (I'm
> leaving out the form because it should not be relevant):
>
> <%@ Language=VBScript %>
> <!--#INCLUDE FILE="clsupload.asp"-->
> <%
> set o = new clsUpload
> if o.Exists("cmdSubmit") then
>
> 'get client file name without path
> sFileSplit = split(o.FileNameOf("txtFile"), "\")
> sFile = sFileSplit(Ubound(sFileSplit))
>
> o.FileInputName = "txtFile"
> o.FileFullPath = Server.MapPath(".") & "\" & sFile
>
> o.save
>
> if o.Error = "" then
> response.write "Success. File save Thank You for the file."
> else
> response.write "Failed due to the following error: " & o.Error
> end if
>
> end if
> set o = nothing
> %>
>
All that was necessary was to use the above code in a separate ASP file
called by the form.

If it works for you, perhaps the problem lies on the ISP's side of things.
I'm still sticking with using IIS 6, since there are so many odd reports of
issues regarding classic ASP and IIS 7.

--
Neil

Neil Gould wrote:
> Bob Barrows wrote:
>> Neil Gould wrote:
>>>>> Here is another repro using clsupload. Exactly what do I have to
>>>>> disable in my browser to make this stop working?
>>>>>
>>>>> <%@ Language=VBScript %>
>>>>> <!--#INCLUDE FILE="clsupload.asp"-->
>>>>>
>>> In comparing this variant with the one currently in use (that
>>> creates
>>> a BLOB object), one functional difference aside from the ActiveX
>>> issue is that the ASP processing code in this one doesn't work if
>>> separated from the form. For example, having a form action =
>>> "someASPfile" that uses the above ASP code and includes
>>> clsupload.asp results in the process failing due to the "object"
>>> being closed.
>>>
>> This does not sound good either. I have several pages working that
>> use this approach (a file-processing page that handles requests from
>> several form pages). Could you show me exactly what I have to do in
>> this ASP code to reproduce your symptoms? Here it is again (I'm
>> leaving out the form because it should not be relevant):
>>
>> <%@ Language=VBScript %>
>> <!--#INCLUDE FILE="clsupload.asp"-->
>> <%
>> set o = new clsUpload
>> if o.Exists("cmdSubmit") then
>>
>> 'get client file name without path
>> sFileSplit = split(o.FileNameOf("txtFile"), "\")
>> sFile = sFileSplit(Ubound(sFileSplit))
>>
>> o.FileInputName = "txtFile"
>> o.FileFullPath = Server.MapPath(".") & "\" & sFile
>>
>> o.save
>>
>> if o.Error = "" then
>> response.write "Success. File save Thank You for the file."
>> else
>> response.write "Failed due to the following error: " & o.Error
>> end if
>>
>> end if
>> set o = nothing
>> %>
>>
> All that was necessary was to use the above code in a separate ASP
> file called by the form.
>
> If it works for you, perhaps the problem lies on the ISP's side of
> things. I'm still sticking with using IIS 6, since there are so many
> odd reports of issues regarding classic ASP and IIS 7

As expected, separating the html form from the asp processing page had no
effect, so there is something else going on. Perhaps you have a parent-paths
issue? Is your html form in a separate folder from the asp page?

--
Microsoft MVP - ASP/ASP.NET - 2004-2007
Please reply to the newsgroup. This email account is my spam trap so I
don't check it very often. If you must reply off-line, then remove the
"NO SPAM"

Bob Barrows wrote:
> Neil Gould wrote:
>> Bob Barrows wrote:
>>> Neil Gould wrote:
>>>>>> Here is another repro using clsupload. Exactly what do I have to
>>>>>> disable in my browser to make this stop working?
>>>>>>
>>>>>> <%@ Language=VBScript %>
>>>>>> <!--#INCLUDE FILE="clsupload.asp"-->
>>>>>>
>>>> In comparing this variant with the one currently in use (that
>>>> creates
>>>> a BLOB object), one functional difference aside from the ActiveX
>>>> issue is that the ASP processing code in this one doesn't work if
>>>> separated from the form. For example, having a form action =
>>>> "someASPfile" that uses the above ASP code and includes
>>>> clsupload.asp results in the process failing due to the "object"
>>>> being closed.
>>>>
>>> This does not sound good either. I have several pages working that
>>> use this approach (a file-processing page that handles requests from
>>> several form pages). Could you show me exactly what I have to do in
>>> this ASP code to reproduce your symptoms? Here it is again (I'm
>>> leaving out the form because it should not be relevant):
>>>
>>> <%@ Language=VBScript %>
>>> <!--#INCLUDE FILE="clsupload.asp"-->
>>> <%
>>> set o = new clsUpload
>>> if o.Exists("cmdSubmit") then
>>>
>>> 'get client file name without path
>>> sFileSplit = split(o.FileNameOf("txtFile"), "\")
>>> sFile = sFileSplit(Ubound(sFileSplit))
>>>
>>> o.FileInputName = "txtFile"
>>> o.FileFullPath = Server.MapPath(".") & "\" & sFile
>>>
>>> o.save
>>>
>>> if o.Error = "" then
>>> response.write "Success. File save Thank You for the file."
>>> else
>>> response.write "Failed due to the following error: " & o.Error
>>> end if
>>>
>>> end if
>>> set o = nothing
>>> %>
>>>
>> All that was necessary was to use the above code in a separate ASP
>> file called by the form.
>>
>> If it works for you, perhaps the problem lies on the ISP's side of
>> things. I'm still sticking with using IIS 6, since there are so many
>> odd reports of issues regarding classic ASP and IIS 7
>
> As expected, separating the html form from the asp processing page
> had no effect, so there is something else going on. Perhaps you have
> a parent-paths issue? Is your html form in a separate folder from the
> asp page?
>
Both HTML and ASP files were in the same directory, and I tried a number of
variants with the same result. The _only_ thing that worked on the ISP is
having the ASP code as part of the HTML form, and that makes no sense to me,
either, since no other functions are dependent on that arrangement. I'm not
even sure what the "object" was, other than the HTML form itself.

At least I have a non-ActiveX, browser-independent set of replacement files
running until this quirk can be sorted out, and it is encouraging to know
that it works somewhere in the world under some configuration or other.

Thanks again for your help.

--
Best,

Neil

Neil Gould wrote:
> Bob Barrows wrote:
>> Neil Gould wrote:
>>> Bob Barrows wrote:
>>>> Neil Gould wrote:
>>>>>>> Here is another repro using clsupload. Exactly what do I have to
>>>>>>> disable in my browser to make this stop working?
>>>>>>>
>>>>>>> <%@ Language=VBScript %>
>>>>>>> <!--#INCLUDE FILE="clsupload.asp"-->
>>>>>>>
>>>>> In comparing this variant with the one currently in use (that
>>>>> creates
>>>>> a BLOB object), one functional difference aside from the ActiveX
>>>>> issue is that the ASP processing code in this one doesn't work if
>>>>> separated from the form. For example, having a form action =
>>>>> "someASPfile" that uses the above ASP code and includes
>>>>> clsupload.asp results in the process failing due to the "object"
>>>>> being closed.
>>>>>
>>>> This does not sound good either. I have several pages working that
>>>> use this approach (a file-processing page that handles requests
>>>> from several form pages). Could you show me exactly what I have to
>>>> do in this ASP code to reproduce your symptoms? Here it is again
>>>> (I'm leaving out the form because it should not be relevant):
>>>>
>>>> <%@ Language=VBScript %>
>>>> <!--#INCLUDE FILE="clsupload.asp"-->
>>>> <%
>>>> set o = new clsUpload
>>>> if o.Exists("cmdSubmit") then
>>>>
>>>> 'get client file name without path
>>>> sFileSplit = split(o.FileNameOf("txtFile"), "\")
>>>> sFile = sFileSplit(Ubound(sFileSplit))
>>>>
>>>> o.FileInputName = "txtFile"
>>>> o.FileFullPath = Server.MapPath(".") & "\" & sFile
>>>>
>>>> o.save
>>>>
>>>> if o.Error = "" then
>>>> response.write "Success. File save Thank You for the file."
>>>> else
>>>> response.write "Failed due to the following error: " & o.Error
>>>> end if
>>>>
>>>> end if
>>>> set o = nothing
>>>> %>
>>>>
>>> All that was necessary was to use the above code in a separate ASP
>>> file called by the form.
>>>
>>> If it works for you, perhaps the problem lies on the ISP's side of
>>> things. I'm still sticking with using IIS 6, since there are so
>>> many odd reports of issues regarding classic ASP and IIS 7
>>
>> As expected, separating the html form from the asp processing page
>> had no effect, so there is something else going on. Perhaps you have
>> a parent-paths issue? Is your html form in a separate folder from the
>> asp page?
>>

Bingo!

Thanks to your encouragement, I went back and tried another approach to
separating the HTML form from the ASP page, and managed to get it working.
At this point, I'm not sure what I was doing wrong before to get the error.
The good news is that I don't have to do much more than extract the code
from the page and "genericize" it a bit.

Thanks again, Bob!

Neil