Variable now, might is wondering, what does he mean, Don ' t skimp on the variables? So, often times it's more
Efficient to "variables to" store results from ADO queries or from objects, and then reference the
Variable as opposed to continuously referencing the object.
For example, your could do this:
If request.querystring ("Name") = "Frank" Then
...
End If
If request.querystring ("Name") = "Steve" Then
...
End If
Response.Write ("Your name is" & Request.QueryString ("name"))
Use the ' Request object ', ASP has to go read the QueryString variable name. You can reduce
This to have to just read this once by doing the following:
Dim StrName
StrName = Request.QueryString ("Name")
If strName = "Frank" Then
...
End If
If strName = "Steve" Then
...
End If
Response.Write ("Your name is" & StrName)
Plus, I Personally the above scenario is easier to read. It ' s easier, I am, to mentally associate
StrName to is the user ' s name as opposed to associating Request.QueryString ("name") as the user ' s name.
Just my two cents, though!
