We have a problem with the objAgent.Querystring in a .asp file.
We have for example the following code:
objAgent.QueryString = "number=4184&othernumber=28"
objAgent.RunScript "xml_number.htm"
When we retrieve the values with the next part code in file
xml_postcode.htm:
def var number as integer no-undo.
def var othernumber as integer no-undo.
assign
number = integer(get-value("number"))
othernumber = integer(get-value("othernumber")).
{&out}
number " " othernumber.
We you retrieve the value of "number" in WebSpeed the result will be for example 900 (this is by the way a number that is used the most). But the strange thing of all is that we have 16 different kinds .asp files and all the files are using the same code. 15 of them are oke, but 1 doesn't work. It look likes that the Querystring doesn't send the correct values to webspeed. We are using the wsasp.dll.
Other strange thing is that we compile xml_number.htm with a different name (for example xml_number2.htm) and use this file instead, the script runs fine.
Does anybody have an idea what the problem could be?
Operating system : Windows 2000 Server (productionserver) / Windows 2003 Server (testserver)
Progress Version : 9.1 D09
IIS : 5.0 (productionserver) / 6.0 (testserver) with wsasp.dll
We have for example the following code:
objAgent.QueryString = "number=4184&othernumber=28"
objAgent.RunScript "xml_number.htm"
When we retrieve the values with the next part code in file
xml_postcode.htm:
def var number as integer no-undo.
def var othernumber as integer no-undo.
assign
number = integer(get-value("number"))
othernumber = integer(get-value("othernumber")).
{&out}
number " " othernumber.
We you retrieve the value of "number" in WebSpeed the result will be for example 900 (this is by the way a number that is used the most). But the strange thing of all is that we have 16 different kinds .asp files and all the files are using the same code. 15 of them are oke, but 1 doesn't work. It look likes that the Querystring doesn't send the correct values to webspeed. We are using the wsasp.dll.
Other strange thing is that we compile xml_number.htm with a different name (for example xml_number2.htm) and use this file instead, the script runs fine.
Does anybody have an idea what the problem could be?
Operating system : Windows 2000 Server (productionserver) / Windows 2003 Server (testserver)
Progress Version : 9.1 D09
IIS : 5.0 (productionserver) / 6.0 (testserver) with wsasp.dll