Basic ADODB Problem

Question

So, I want to implement a simple database project using VB 6 and Oracle 10g. A friend of mine who has done a similar project, sent me some sample of his code because I am new to DB programming. I had already implemented a simple working code. Here is the comparison:
rs is the ADODB.recordset object
and dbipl is the ADODB.connection object
team is the tablename
name is a column in the table
His code:
dbipl.Open "dsn=new;user id=system;password=pass;"
rs.CursorType = adOpenStatic
rs.CursorLocation = adUseClient
rs.LockType = adLockOptimistic
rs.Open "select * from team", dbipl, , , adCmdText
Do While Not rs.EOF = True
list.AddItem rs.Fields("name")
rs.MoveNext
Loop
rs.Close
dbipl.Close
My Code:
dbipl.Open "dsn=new;user id=system;password=pass;"
set rs = db.Execute("select * from team")
Do While Not rs.EOF = True
list.AddItem rs("name")
rs.MoveNext
loop
rs.close
dbipl.Close
I am not using the Fields keyword anywhere in my code. Also, he hasn't used the INSERT or UPDATE statements in his entire code because he is using something like this to update or insert records:
rs.AddNew
rs.Fields(0) = Text1.Text
rs.Fields(1) = Text2.Text
rs.Update
I though we have to use the SQL statements like this:
set rs = db.Execute("insert into table values (......)")
I am guessing his advantage is that he doesn't need to use SQL statements for inserting records or updating his tables. I am completely lost and I don't know which method to use. Please clarify the difference in the two methods. Thank you for your time.

Answer 1

Pratham wrote:
Also, he hasn't used the INSERT or UPDATE statements in his entire code because he is using something like this to update or insert records:
rs.AddNew
rs.Fields(0) = Text1.Text
rs.Fields(1) = Text2.Text
rs.Update
I though we have to use the SQL statements like this:
set rs = db.Execute("insert into table values (......)")The AdoDB class generates that SQL itself if you do not explicitly provide a SQL statement. In fact, from long past experience doing Windows client development, drivers like AdoDB can be quite noisy and generate all kinds of SQL statements for "managing" the database client-server session - totally unbeknown to the developer whose code that AdoDB driver is executing. This can cause anything from a performance knock to unexpected run-time behaviour.
Back then I always used the "+passthru+" option - telling the driver to bug out and only do the SQLs I explicitly coded and nothing else.
No idea how the "modern" driver behaves... but I would think that not much have changed.
If you do have to use SQL from your client code, then rather use explicit SQL. Code it yourself. Use bind variables (critical!). Use bulk binding. Do not rely on the driver to generate the appropriate and optimised SQL for you. It is seldom able to do it as well as hand crafted SQL.