Visual Basic

Public Module Foo
   Public Sub Test()
   End Sub
End Module

Public Class Bar
   Public Sub Main()
      Foo.Test()    ' Can be called like this.
      Test()        ' Or like this, without specifying the module name.
   End Sub
End Class

shiroamachi wrote:

how about connection and recordset object? Do we need to call the close method and set the object to nothing?

shiroamachi wrote:

When to call open and close method of connection and recordset object in a procedure/function with try catch? Is it ok to put in "finally" ?

try<br />
dim con as connection<br />
dim rs as recordset<br />
con.open()<br />
rs = con.execute(sqlstring)<br />
<br />
catch ex as Exception<br />
<br />
msgbox "error"<br />
exit sub<br />
<br />
finally<br />
<br />
rs.close()<br />
con.close()<br />
<br />
end try

shiroamachi wrote:

assume there's error in con.open() and the error was catch and then do finally. in finally, because of rs is not yet open, will cause error cant close object that isnt open. How to resolve this problem?

if con.State = adStateOpen then
   con.Close()
end if

If (con.State <> ConnectionState.Closed) Then
   con.Close()
End If

Imports Shell32
.
.
.
Public Class Form1
 
    Private Sub Button1_Click(blah, blah) Handles Button1.Click
        Dim myShellObject As New Shell32.Shell
        myShellObject.Open(ShellSpecialFolderConstants.ssfDRIVES)
    End Sub
 
End Class