how to called open and closed methods of connection from one module to other.

Question

0.00/5 (No votes)

See more:

i have write this code for module:

VB

Module Module1
Public Class cn
       Public Shared con As New SqlConnection

       Public Shared Sub openconnection()
           con = New SqlConnection("Data Source=.\sqlexpress;Initial Catalog=PROJ;Integrated Security=True")
           con.Open()
       End Sub

       Public Shared Sub close()

           con.Close()
       End Sub
   End Class
end module

my problem is i want to used this code for opening and closing connection that i used for multiple forms.
Can this code is work and how can i call this methods or used this codes.That is my main aim is to minimized codes and code re usability. how can i achieved this.
i am using vb.net 2010 and back end sql server 2008. There is any alternative for this types of implementation.
waiting for some help..

Posted 19-Sep-12 2:24am

neldesai

Updated 19-Sep-12 2:26am

Wes Aday

v2

Add a Solution

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

**Andrei Straut** · Accepted Answer · 2012-09-19T02:39:00

Having multiple forms, you could make a singleton class that wraps around your connection. Then when calling your singleton instance, check if that connection is already open, and if it is, you don't open it again.

As you seem to be in luck today (I don't usually post code, but I am doing this kind of work as we speak, although I don't need to keep connections open across forms), I'll post you some stuff with basic comments:

C#

class DatabaseServiceOracle {
    private static DatabaseServiceOracle instance;
    private static OracleConnection connection;

    //Empty private constructor, we don't want multiple instances of this class
    private DatabaseServiceOracle() {}

    /*Use this to acquire a reference to present class, and make sure 
    that reference never points to a null object*/
    public static DatabaseServiceOracle getInstance() {
    	if(instance == null) {
            instance = new DatabaseServiceOracle();
    	}
    
    	return instance;
    }

    public OracleConnection getConnection() {
        if(connection == null) {
            //Init your connection here
        }

        /*We don't normally open connections when acquiring them, but we
        do it on a per-need basis*/
        if(connection.State != ConnectionState.Open) {
            connection.Open();
        }

        return connection;
    }
}

Also, don't mind the formatting, although the code is C#, we have an internal convention that says we use the Java formatting conventions even when we do C#.

Also, the database system is Oracle and not SQL Server, but the point stands.

Furthermore, this is conceived for an MVC system, so in here would go most of the DB queries needed (it's just a basic template that we customize for our needs)