How to avoid hard coding the connection string in VB.NET windows application?

Question

0.00/5 (No votes)

See more:

Hello, I'm still a newbie so please pardon my question. I just want to know how to avoid hard coding the connection string in every sub in vb.net. I'm using vb.net 2017 and access as my database. I have multiple connections to my database and I want to know if there is an efficient way to this?

Below is my connection string and I put it in a module so every form that I have made can access it and I just need to call the "conSTR" variable.

What I have tried:

Public conSTR As String = "Provider=Microsoft.ACE.OLEDB.12.0;Data Source=D:\VBactivity\PAGEANT\PAGEANT.accdb"

and below is how I used the conSTR variable

Using cons As New OleDb.OleDbConnection(conSTR)

    Using cmd As New OleDb.OleDbCommand


        With cmd
            .CommandText = "INSERT INTO Category (CategoryName, CatPercent) VALUES (@Category ,@CatPercent)" ', @CatPercent)"
            .Parameters.AddWithValue("@Category", txtCategory.Text)
            .Parameters.AddWithValue("@CatPercent", numCategory.Value)
            .Connection = cons
            cons.Open()
            cmd.ExecuteNonQuery()
            cons.Close()
            MessageBox.Show("CATEGORY HAS BEEN ADDED", "CATEGORY", MessageBoxButtons.OK, MessageBoxIcon.Information)
        End With


    End Using


End Using

Posted 29-Mar-20 15:42pm

lelouch_vi 2

Updated 2-Apr-20 18:06pm

Add a Solution

Comments

Maciej Los 30-Mar-20 1:35am

If conSTR is a variable of public scope, you don't need to pass it into procedure. See:
Scope - Visual Basic | Microsoft Docs[^]
How to: Control the Scope of a Variable - Visual Basic | Microsoft Docs[^]
You can define connection string in ap.config file. See: Connection Strings and Configuration Files - ADO.NET | Microsoft Docs[^]

Tomas Takac 30-Mar-20 1:56am

Store the connection string in config file: Connection Strings and Configuration Files - ADO.NET | Microsoft Docs[^]

lelouch_vi 2 4-Apr-20 3:22am

Thank you for pointing that out. Now I realize it already why hard coding connection string is a bad idea. I already have my connection string to my app.config.

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)

Member 11359369 · Accepted Answer · 2020-04-02T18:07:00

VB

'Create a Module and Create Fuction Connect 
' You can connect From database local or network area 
Public Sub connect()
Public Con As New OleDbConnection
        M_drivepath = Left(Application.StartupPath, 1)
        If My.Computer.Name.ToString() = "MSERVER" Then
            Con.ConnectionString = "Provider=Microsoft.ACE.OLEDB.12.0;Data Source=E:\WIN_SOFT\RETAIL_SOFT\Datafile\DATA" & aWork_Data & ".accdb;Jet OLEDB:Database Password=M1423456"
        Else
            Con.ConnectionString = "Provider=Microsoft.ACE.OLEDB.12.0;Data Source=Z:\WIN_SOFT\RETAIL_SOFT\Datafile\DATA" & aWork_Data & ".accdb;Jet OLEDB:Database Password=M1423456""
        End If
       
      
        Brn_File = "SDBRN14"    ' SDBRN14 IS TABLE NAME STORE IN Brn_File
    Con.Open()
    End Sub
' Where you want to Connect Database write Connect 
' else Check Connection Open or not
' Write Command   If Con.State = ConnectionState.Closed Then Con.Open()