Global.asa good practice?

[Andyza]

In my Global.asa file I have the following 2 subs for opening and
closing my db connection:

Sub OpenConn()
Dim conn
Set conn = Server.CreateOb ject("ADODB.Con nection")
conn.Open Application("Co nnString")
End Sub

Sub CloseConn()
conn.Close
Set conn = nothing
End Sub

Then in my asp pages I simply call the subs when I need to open and
close the db connection.

Eg.:

Dim Test
Test = "Select XXX from SomeTable"
OpenConn()
Set rs = conn.Execute(Te st)
Do While Not rs.eof
Response.Write( rs("XXX"))
rs.MoveNext()
Loop
CloseConn()

Is this good practice to have the 2 db subs in the Global.asa?

[Andyza]

Ok, bad idea! I wasn't thinking! It won't work - the subs will be out
of scope in the Global.asa...

[Bob Barrows [MVP]]

Andyza wrote:

Ok, bad idea! I wasn't thinking! It won't work - the subs will be out
of scope in the Global.asa...

Not only that, but read this:
http://www.aspfaq.com/show.asp?id=2053

Bob Barrows
--
Microsoft MVP -- ASP/ASP.NET
Please reply to the newsgroup. The email account listed in my From
header is my spam trap, so I don't check it very often. You will get a
quicker response by posting to the newsgroup.

[Aidy]

As you have found out, that doesn't work, but you can put those pages in a
separate file and INCLUDE them in each ASP page you need them.

"Andyza" <an****@webmail .co.za> wrote in message
news:11******** **************@ g47g2000cwa.goo glegroups.com.. .

In my Global.asa file I have the following 2 subs for opening and
closing my db connection:

Sub OpenConn()
Dim conn
Set conn = Server.CreateOb ject("ADODB.Con nection")
conn.Open Application("Co nnString")
End Sub

Sub CloseConn()
conn.Close
Set conn = nothing
End Sub

Then in my asp pages I simply call the subs when I need to open and
close the db connection.

Eg.:

Dim Test
Test = "Select XXX from SomeTable"
OpenConn()
Set rs = conn.Execute(Te st)
Do While Not rs.eof
Response.Write( rs("XXX"))
rs.MoveNext()
Loop
CloseConn()

Is this good practice to have the 2 db subs in the Global.asa?