MS Access (ADO): AddNew/Delete/Update vs. SQL statements

Posted on 2004-09-17
Last Modified: 2013-12-25
I have an application that uses a MS Access database via Jet 4.0.

1) Which is better to implement, using the AddNew/Delete/Update way or using SQL statements, e.g. INSERT/DELETE/UPDATE to add, delete and update records in the database?

Please explain why and to give code snippets re:how to use the better implementation.

2) What type of error handling should be implemented when the database functions are unsuccessful?

If possible, please give code snippets.


Question by:halfondj
  • 5
  • 3
  • 2
  • +4
LVL 29

Assisted Solution

leonstryker earned 100 total points
ID: 12088755
Depends on your application.  I like using SQL, it is more flexiable and does not require a constent conneciton to the database.  in addition you can not .Update a recordset if it was based on a joined tables.

LVL 49

Assisted Solution

by:Ryan Chong
Ryan Chong earned 50 total points
ID: 12090386
Definitely is using SQL Statement, more faster (and no need to declare Recordset Object), but if you want to return the recordset object after a record is added, deleted or updated, you can consider to use AddNew/Delete/Update methods

Author Comment

ID: 12091187
I tried using SQL, but was unsuccessful - do I have to use .BeginTrans, .CommitTrans, etc.?

I thought you had to declare a record set when doing an add/delete or update.

For the 500 points or a split, please provide code snippets.

LVL 18

Accepted Solution

Sethi earned 275 total points
ID: 12091412
1. Direct SQL execution will be more optimal anytime as the execution takes place directly on the server and no resources are wasted for the recordset. You can find code snippets at the following links:

Also search for more examples on ADO code.

2. One should display an error message and stop further execution of code so that no more errors from that point are enountered. Errors related to database should not be taken lightly. So do not use Resume statements.

Author Comment

ID: 12091490
Thanks for the reply.  The samples are great.

One more question: Is it good to use .BeginTrans, .CommitTrans, .Rollback, etc?  I have a very simple application and being new to DB programming, I don't know what's the best way of implmenting things.

If it's good to do it, please show an example.

Thanks again!
LVL 18

Assisted Solution

Sethi earned 275 total points
ID: 12091531
I do not use it in my applications with Access :-) and no way with a small application.

Assisted Solution

x50Fade earned 75 total points
ID: 12099942
I sometimes use transactions with routines in my apps....

Only routines that are very delicate, and that must be able to "roll back" if something went wrong.

On error goto err_handler

'Code Here..........

exit sub

Find Ransomware Secrets With All-Source Analysis

Ransomware has become a major concern for organizations; its prevalence has grown due to past successes achieved by threat actors. While each ransomware variant is different, we’ve seen some common tactics and trends used among the authors of the malware.


Author Comment

ID: 12101291
Thanks everyone for your replies.  They were all great.
LVL 12

Expert Comment

ID: 12101323

Wheter you use SQL or VBA depends on your exact requirements.

In a distributed environment, SQL is probably preferred, since the code runs on the server. Other than previous posters, I found that VBA is in many cases faster than SQL since you can optimize the code for a specific task; the SQL engine can't do this since it doesn't know what you want to achieve.

Some Examples (off the top of my head, not verified):

SQL:   UPDATE MyTable SET FieldA = "bla" WHERE FieldB = "anykey"

VBA:   Dim RS as Recordset
          Set RS = CurrentDB.OpenRecordset("SELECT * FROM MyTable")
          RS.FindFirst "FieldB='anykey'"
          RS("FieldA") = "bla"

Obviously, the VBA is longer and in this example, it might even be slower. However, if you need to iterate through a set of records, VBA will be faster:

    SQL = "SELECT COUNT (FieldA) FROM MyTable";
    n = DoCmd.ExecSQL(SQL)
    For i = 1 to n
       SQL = UPDATE MyTable SET FieldA = "bla" & i WHERE FieldB = "anykey" & i
       DoCmd.ExecSQL SQL
    Next i

   Dim RS as Recordset
   Set RS = CurrentDB.OpenRecordset("SELECT * FROM MyTable ORDER By anykey")
   n = RS.RecordCount
   While NOT RS.EOF
       RS("FieldA") = "bla" & i

Again, the VBA is longer, but I believe it will be significantly faster, because all the overhead of processing SQL is not required.
- can be used to increase performance, especially in a distributed environment.
- can be used to make sure that either all or no change on the DB will occur.
You wan't need transactions normally, however, they can come very handy in specific situations.

Hope this helps

LVL 18

Expert Comment

ID: 12101329
Good to hear that...thanks for the points :-)

Author Comment

ID: 12104914
To fulscher: Thanks for your explaination.  It was very well done.  I would have certainly given you points too. :).
LVL 12

Expert Comment

ID: 12105205
Well, I was a bit late. Hope you can use some of the stuff, anyway.


Author Comment

ID: 12106706
Definitely.  I owe you :).

Expert Comment

ID: 13873436
i am doing one project vb with msaccess 97 ,i am connected all command add,select delete ,
this add commands for example i am add to the name via vb to msaccess that particular names are added ,but i want that name already here recently add a name not checked

Featured Post

How your wiki can always stay up-to-date

Quip doubles as a “living” wiki and a project management tool that evolves with your organization. As you finish projects in Quip, the work remains, easily accessible to all team members, new and old.
- Increase transparency
- Onboard new hires faster
- Access from mobile/offline

Join & Write a Comment

Introduction While answering a recent question about filtering a custom class collection, I realized that this could be accomplished with very little code by using the ScriptControl (SC) library.  This article will introduce you to the SC library a…
When trying to find the cause of a problem in VBA or VB6 it's often valuable to know what procedures were executed prior to the error. You can use the Call Stack for that but it is often inadequate because it may show procedures you aren't intereste…
Show developers how to use a criteria form to limit the data that appears on an Access report. It is a common requirement that users can specify the criteria for a report at runtime. The easiest way to accomplish this is using a criteria form that a…
This lesson covers basic error handling code in Microsoft Excel using VBA. This is the first lesson in a 3-part series that uses code to loop through an Excel spreadsheet in VBA and then fix errors, taking advantage of error handling code. This l…

757 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

22 Experts available now in Live!

Get 1:1 Help Now