Yes, I did. In my OP, you can see it:
'''''''''''''''''''''''''''''''''''''''''''''''''' ''''
I tried doing this:
Dimm conn
conn = GetDBConnection()
conn.Close
but it errors out with
******************************************
Object required: 'Provider=MSDAORA.1;P'
******************************************
I did the following now:
***************************
' RECORDSET
Set rs=Server.CreateObject("ADODB.Recordset")
rs.ActiveConnection = GetDBConnection()
' GET SOMETHING
strSql = "SELECT XXX"
rs.Open strSql
' DO SOMETHING WITH RS
rs.Close
Set rs = nothing
*********************************
Now when I read about ADO connection (link below) does it mean it is implementing some sort of connection pooling?? It will be hard for me to get answers from the server folks nor can I monitor any connection to the Oracle server. Just want to make sure I don't tied up any unnecessary resources or wait for IIS/Oracle to timeout any open connection.
http://www.w3schools.com/ado/prop_comm_activeconn.asp
The ActiveConnection property tells which Connection object the Command object belongs to.
If the connection is closed, it sets or returns a definition for a connection. If the connection is open it sets or returns the current Connection object.
EDIT -- I did this now: rs.ActiveConnection.Close
Can someone clarify how the bold item above works? Can someone provide sample code on how to implement it?
Most examples I've found usually have all the connection, sql, rs, close all in 1 ASP script.