Hi. We have an old ugly application that uses ASP 3.0.
We had to move it to another server recently (basically by copying it
and setting up in IIS), and as we did, we started experiencing
problems with VB.
The code that somehow worked on the old server produces errors. The
most frequent example is
If Request("ddlFil ter") then ....
It worked on the old server, now it gives us a type mismatch error.
Also, the errors about index not being in the collection (such as
recordset column) were swallowed (didn't occur) before and now they
actually occur, overall it's like VB went to "strict mode" or
something.
How do we make it lax again? Rewriting all that legacy code will be a
pita
We had to move it to another server recently (basically by copying it
and setting up in IIS), and as we did, we started experiencing
problems with VB.
The code that somehow worked on the old server produces errors. The
most frequent example is
If Request("ddlFil ter") then ....
It worked on the old server, now it gives us a type mismatch error.
Also, the errors about index not being in the collection (such as
recordset column) were swallowed (didn't occur) before and now they
actually occur, overall it's like VB went to "strict mode" or
something.
How do we make it lax again? Rewriting all that legacy code will be a
pita