Database Application

I have reviewed your code. It's nice but there is a problem with interacting COM objects with .NET objects. In your example, you interopped Microsoft ActiveX DataObjects with your .NET application. Microsoft ActiveX Data Object is a COM library. As we all know, much of the previous COM implementations (VB6, VC++6 etc) had been replaced or updated when .NET was introduced. So instead of creating an ADODB.Recordset object for Inserting new records, you can just use OleDbCommand to the the record insertion. Example: Using cmd as New OleDbCommand cmd.Connection = conn cmd.CommandText = "Insert into table SET column [email protected]" cmd.Parameters.Add("@value", OleDbType.Varchar).Value = value cmd.ExecuteNonQuery() End Using Also using OleDbCommand parameters reduce SQL injection attacks, which makes your application safer. Although COM and .NET interop is possible, for optimization, if it is possible in .NET, do it in .NET.

sir cedrick, i kinda like your post, it fits on my current project.. i am new in VB.net and still studying it. i quoted the code here: rs = New ADODB.Recordset rs.Open("Select * from administrator", cnstring, ADODB.CursorTypeEnum.adOpenKeyset, ADODB.LockTypeEnum.adLockOptimistic) rs.AddNew() rs("username").Value = txtusername.Text rs("password").Value = txtpassword.Text rs.Update() MsgBox("Save!", MsgBoxStyle.Information, "Save") txtpassword.Text = "" txtusername.Text = "" gridview1.Refresh() i just want to ask what is the meaning of this line: rs = New ADODB.Recordset rs.Open("Select * from administrator", cnstring, ADODB.CursorTypeEnum.adOpenKeyset, ADODB.LockTypeEnum.adLockOptimistic) thanks alot!