Session Variables and reclaiming associated memory.

[Mario]

If there is an associated memory cost for using session variables, can
the memory used be reclaimed on an ASP page by setting the session
variable to undefined or null? If on the same ASP page you use a
different session variable name and after each refresh of the page,
set the previous session variable to undefined before using the next
session variable, does this reclaim the memory used in the previous
session variable, or does the usage of memory just continue to grow
with each page refresh?

Tex

[swp]

mp*******@satx.rr.com (Mario) wrote in message news:<53**************************@posting.google. com>...

If there is an associated memory cost for using session variables, can
the memory used be reclaimed on an ASP page by setting the session
variable to undefined or null? If on the same ASP page you use a
different session variable name and after each refresh of the page,
set the previous session variable to undefined before using the next
session variable, does this reclaim the memory used in the previous
session variable, or does the usage of memory just continue to grow
with each page refresh?

Tex

When you say "undefined" above do you mean "nothing" or ""?

for example, which of these is appropriate to your situation:
DIM con, rs, sql
sql = "SELECT name, addr1, addr2, city, state, zip FROM people WHERE
flag<>'D' ORDER BY name"
set con = server.CreateObject("ADODB.Connection")
con.Open db_name, username, password ' fill in with your own system
dsn link and connectivity information
set rs = con.execute(xsql)
.... process stuff ...
con.close
set rs = nothing
set con = nothing

swp