Difference between DBEngine.BeginTrans and DBEngine.Workspaces(0).BeginTrans

calendar_today Asked Jan 7, 2009
thumb_up 7 upvotes
history Updated April 14, 2026

Direct Answer

Have a look here: DAO Workspace And then here: DAO Workspace: Opening a Separate Transaction Space (The links are for MFC, but they're applicable to whatever you're coding in.)…. This is an advisory response with reference links, ranked #31st of 67 by community upvote score, from 2009.


The Problem (Q-score 6, ranked #31st of 67 in the Access VBA archive)

The scenario as originally posted in 2009

In Access, what is the difference between these two statements?

DBEngine.BeginTrans

and

DBEngine.Workspaces(0).BeginTrans

The documentation for both leads to the same place.

Why community consensus is tight on this one

Across 67 Access VBA entries in the archive, the accepted answer here holds niche answer (below median) status — meaning voters are unusually aligned on the right fix.


The Verified Solution — niche answer (below median) (+7)

Advisory answer — community consensus with reference links

Note: the verified answer below is a reference / advisory response rather than a copy-ready snippet.

Have a look here: DAO Workspace
And then here: DAO Workspace: Opening a Separate Transaction Space

(The links are for MFC, but they’re applicable to whatever you’re coding in.)

DBEngine.Workspaces(0) is the default workspace. Other workspaces can be created, which let you work with separate sessions; the idea is that BeginTrans and EndTrans apply to the whole workspace, but if you need to do stuff outside that transaction, you can create another workspace and use it independently of your transactions in the first workspace.

Personally, I never had occasion to use more than one workspace when doing DAO in VBA. * shrug *


When to Use It — vintage (14+ years old, pre-2013)

Ranked #31st in its category — specialized fit

This pattern sits in the 77% tail relative to the top answer. Reach for it when your scenario closely matches the question title; otherwise browse the Access VBA archive for a higher-consensus alternative.

What changed between 2009 and 2026

The answer is 17 years old. The Access VBA object model has been stable across Office 2013, 2016, 2019, 2021, 365, and 2024/2026 LTSC, so the pattern still compiles. Changes that might affect you: 64-bit API declarations (use PtrSafe), blocked macros in downloaded files (Mark-of-the-Web), and the shift toward Office Scripts for web-first workflows.

help
Frequently Asked Questions

This is a below-median answer — when does it still fit?
expand_more

Answer score +7 vs the Access VBA archive median ~4; this entry is niche. The score plus 6 supporting upvotes on the question itself (+6) means the asker and 6 subsequent voters all validated the approach.

This answer links out — what are the reference links worth following?
expand_more

Read the first external link for the canonical reference, then search this archive for a top-10 entry in the same category — advisory answers are best paired with a ranked code snippet to close the loop.

This answer is 17 years old. Is it still relevant in 2026?
expand_more

Published 2009, which is 17 year(s) before today’s Office 2026 build. The Access VBA object model has had no breaking changes in that window. Three things to re-test: (1) blocked macros on downloaded files (Mark-of-the-Web), (2) 64-bit API declarations (PtrSafe, LongPtr), (3) any shift toward Office Scripts for web scenarios.

Which Access VBA pattern ranks just above this one at #30?
expand_more

The pattern one rank above is “Combine values from related rows into a single concatenated string value”. If your use case overlaps, compare both before committing.

Data source: Community-verified Q&A snapshot. Q-score 6, Answer-score 7, original post 2009, ranked #31st of 67 in the Access VBA archive. Last regenerated April 14, 2026.