This script causes NP Pool to exhaust itself - can't see why - very simple

[Freebase]

Something changed recently on our W2K SP4 machine when we installed
INTERSOLV ODBC software... the following script just opens a connection
to an MS-Access DB, gets a record then tears down the connection

<%
tpl_ConnectString = "DRIVER={Microsoft Access Driver (*.mdb)};
DBQ=g:/inetpub/wwwroot/servers/xta_db/tpl.mdb"
query = "select tpl_text from templates where tpl_name='showart_top'"
response.buffer=false
for i=1 to 100

on error resume next
set Conn = Server.CreateObject("ADODB.Connection")
if (err.number <0 ) then
response.write "Error creating Connection in getrecordset,
number=" & err.description
end if
on error resume next
conn.open TPL_ConnectString
if (err.number <0 ) then
response.write "Error opening Connection in getrecordset,
number=" & err.description
end if

on error resume next
Set rs = Server.CreateObject("ADODB.Recordset")
if (err.number <0 ) then
response.write "Error creating Recordset in getrecordset, number="
& err.description
end if

on error resume next
rs.open query,conn
if (err.number <0 ) then
response.write "Error executing query in
getrecordset(get_template), number=" & err.description
else
xxx=rs("tpl_text")
end if

response.write "loop=" + cstr(i)+"..size of
tpl="+cstr(len(xxx))+"<p>"

rs.close
if (err.number <0 ) then
response.write "Error closing Recordset in getrecordset, number=" &
err.description
end if

on error resume next
rs=nothing
if (err.number <0 ) then
response.write "Error setting to nothing Recordset in getrecordset,
number=" & err.description
end if

on error resume next
conn.close
if (err.number <0 ) then
response.write "Error closing conn in getrecordset, number=" &
err.description
end if

on error resume next
conn=nothing
if (err.number <0 ) then
response.write "Error setting conn to nothing in getrecordset,
number=" & err.description
end if
next
When we run this script now, we can see NP Pool climb in the
DLLHOST.EXE process until it hits about 1,000K , then we get 'system
resource exceeded'.... I've looked everywhere for a clue as to what's
changed , but can't find it... I know it has something to do with MDAC
and the Access driver, but another system we have that does not have
the INTERSOLV installed, does not run out of NP Pool..

My question is... what could possibly be exhausting NP Pool when an
Access db is connected to, retrieved from, followed by a close
recordset, set to nothing, close connection, set to nothing ???