R
Raga
Hi,
We have found a very freakish ‘truncate’ behavior in Classic ASP application
(that is called from within a web logic portal).
We have an ASP variable, lngOrderId (an oracle sequence number that right
now running in 8000+) in our ASP page.
The current value of this variable (got from the session) is 8095.
In order to pass the value to the next page, we set the variable’s value to
a Hidden INPUT field and pass it to the next form.
Here is the code snippet that does this task:
Response.Write "<!— Sample debug write " & lngOrderId & " -->"
strHTMLString = strHTMLString & "<input type=""hidden"" name=strOrdID
value=""" & lngOrderId & """>"
Response.Write strHTMLString
Now the first line correctly displays 8095 in the ViewSource.
But in the same view source I see that the above hidden variable (strOrdID)
has a value of 95 !
This happens only with particular variable and does not affect the other
variables.
We are unable to reason out why this is happening and it looks very very
freakish.
One weirdness in this scenario is – the ASP application is called from
within a weblogic portal.
Could this be a bug in ASP? Any ideas?
Thanks,
Raga
We have found a very freakish ‘truncate’ behavior in Classic ASP application
(that is called from within a web logic portal).
We have an ASP variable, lngOrderId (an oracle sequence number that right
now running in 8000+) in our ASP page.
The current value of this variable (got from the session) is 8095.
In order to pass the value to the next page, we set the variable’s value to
a Hidden INPUT field and pass it to the next form.
Here is the code snippet that does this task:
Response.Write "<!— Sample debug write " & lngOrderId & " -->"
strHTMLString = strHTMLString & "<input type=""hidden"" name=strOrdID
value=""" & lngOrderId & """>"
Response.Write strHTMLString
Now the first line correctly displays 8095 in the ViewSource.
But in the same view source I see that the above hidden variable (strOrdID)
has a value of 95 !
This happens only with particular variable and does not affect the other
variables.
We are unable to reason out why this is happening and it looks very very
freakish.
One weirdness in this scenario is – the ASP application is called from
within a weblogic portal.
Could this be a bug in ASP? Any ideas?
Thanks,
Raga