VB.NET Database Access

take a look here:
http://support.microsoft.com/kb/301248

The general procedure is same:

1: you define a connection and set its connecton string and open it

2: you define a command object and set its text .

3: Now you can run this command:

For example:
Dim cmdDB As New SqlCommand("Update MyTable Set Age=6 where name="James"

If you are starting, seriously have a look at Entity FrameWork. It will generate the complete DAL for you. If you can get Julie Lerman's book (http://thedatafarm.com/main.aspx), it would really help you. Also have a look at the "articles" available from the same web site.

My Comments continued:

You can also use a command object to run a stored procedure to update the DB .This method is up to 15% faster as SQL gets compiled on DB.

so to summarize:

1: If you are dealing with a small application, then using Command object with SQL as its command text is sufficient.

2: If you are part of  a company team of developers, dealing with huge application and someone else is responsible for writing stored procedures, then use command which run stored procedure to update the data.

Hi,

I am using the following code...

The code gets the data and bounds it to the correct controls, but if I edit the controls value and click the update button the changes are not save back to the database...

    Private Sub frm_Users_Load(sender As System.Object, e As System.EventArgs) Handles MyBase.Load
        Dim conn As New SqlConnection(")

        Dim cmd As New SqlCommand("proc_UserAccess_All", conn)

        cmd.CommandType = CommandType.StoredProcedure
        cmd.CommandTimeout = 30
        conn.Open()

        da = New SqlDataAdapter(cmd)

        Dim builder As SqlCommandBuilder = New SqlCommandBuilder(da)
        ds = New DataSet()
        da.Fill(ds, "tbl_Users")

        BindingSource1.DataSource = ds.Tables("tbl_Users")
        BindingNavigator1.BindingSource = BindingSource1

        cmd.Dispose()
        cmd = Nothing
        conn.Close()
        conn = Nothing

        txtWindowsUsername.DataBindings.Add("Text", BindingSource1, "UserID")
        txtName.DataBindings.Add("Text", BindingSource1, "Username")
        cbActive.DataBindings.Add("Checked", BindingSource1, "Active")

    End Sub

    Private Sub ToolStripButton1_Click(sender As System.Object, e As System.EventArgs) Handles ToolStripButton1.Click
        Me.Validate()
        Me.da.Update(Me.ds.Tables("tbl_Users"))
        Me.ds.AcceptChanges()

    End Sub

Select allOpen in new window

Do i need to add an addition stored procedure for the update command?

Do i need to add an addition stored procedure for the update command? 

Select allOpen in new window

Yes you do.

Binding data does not mean data gets updated where user presses enter. Every time data changes you need to update data yourself(Using a simple command object or a stored procedure).

Take a good look at strongly typed datasets.   You can define them from within Visual Studio.  I typically will have VS create my CRUD stored procedures as part of defining the dataset.

Once you have a strongly typed dataset, it is quite easy to databind it to a form.  ADO.Net uses disconnected datasets, so binding will update the copy in memory, but you have to run the update command on the dataset to actually persist it out to the database.

Please could someone provide an example of what needs to be changed in my code?

Thank you all for your help I used the link emoreau supplied in the end and managed to get it working (although it may be overcomplicated... but I can trim it down later).