Currentdb.execute update

If part of a statement executed with dbFailOnError failed, the entire statement would be rolled back. To improve performance, these implicit transactions were removed starting with version 3. If you are updating older DAO code, be sure to consider using explicit transactions around Execute statements. For best performance in a Microsoft Access workspace, especially in a multiuser environment, nest the Execute method inside a transaction. Use the BeginTrans method on the current Workspace object, then use the Execute method, and complete the transaction by using the CommitTrans method on the Workspace.

This saves changes on disk and frees any locks placed while the query is running. This example demonstrates the Execute method when run from both a QueryDef object and a Database object. Skip to main content. Jan 6, Freshman. Replies 7 Views Apr 10, abdullahkhan. Solved CurrentDB. Execute Syntax. Replies 14 Views Apr 9, NauticalGent. Solved Duplicate records changing a field with VBA.

Replies 12 Views Dec 10, Cris VS. Search related threads. Remove From My Forums. Answered by:. Archived Forums. Access for Developers. Sign in to vote. Hi, having the following errors with code below. Monday, February 17, PM. As you are returning rows from one table only you do not need to qualify the column names with the table name. Ken Sheridan, Stafford, England. Tuesday, February 18, AM. You don't seem to have any space between the concatenated Strings.

Wednesday, February 19, PM. Have you debugged the code and examined the value of the strSQL variable? Thursday, February 20, PM. Dates has to be enclosed between tags. As Strings to be enclosed between single or double quotes. Once this String is created, did you copy and paste it into the QBE, as mentioned earlier? If so were you able to get any Result set or any errors? You are passing in too few parameters.

Community Bot 1 1 1 silver badge. Jerry Jerry Add a comment. Active Oldest Votes. If the table is locked, is there a way I can unlock it? This simplified code sample should clarify what's going on.

OpenRecordset strSql rs. Edit CurrentDb. Edit One way you found to avoid the error was by adding rs. Improve this answer. HansUp HansUp I think I understand that bit better now. It does make sense that rs.

Edit would lock the table. One thing though, I tried to change the update to target a different row and this failed with the original code , which tells me that the whole table is locked as opposed to certain rows?

Do you have any advice on this aspect? In my test, Edit also locked the entire table, not just the current recordset row. However, as a time-saver for me, I said "perhaps" Not sure how well I understand the rest of your comment. Does it contribute to the problem? Basically, make a copy of the problem code, discard anything which is irrelevant and focus your attention and ours! Okay, fair enough on the perhaps, I was more focusing on your second point the second time I read your question!

I see your point now and removed some bits.