How to Fix Microsoft Access DAO Recordset Update Error 3709 and Crashes
Question details
Users need to resolve runtime error 3709 and unexpected application crashes that occur when updating DAO recordsets in Microsoft Access.
- Product
- Microsoft Access
- Device & OS
- not provided
- Scenario
- Executing UPDATE statements or editing DAO recordsets via code in custom Access database applications.
- Observed behavior
- The application throws runtime error 3709 or completely crashes and closes during the recordset update process on specific Office builds.
Before making changes, verify your current Microsoft Office build version under your Account settings and ensure you have administrative privileges to install updates or revert your installation.
Update Microsoft Access to Version 2211 or Later
The most effective solution is to update Office to a newer build where Microsoft has officially fixed the DAO recordset bug.
Microsoft identified the runtime error 3709 and related crashing behaviors as a bug in specific Office builds. The issue was fully patched in Access version 2211 (build 16.0.15831.20122).
Launch Microsoft Access and open a blank database. Click on 'File' in the top-left corner, then select 'Account' (or 'Office Account') from the bottom left menu.
Under the Product Information section, locate and click the 'Update Options' drop-down button.
Select 'Update Now' to force Office to check for and install the latest updates. Ensure it updates to Version 2211, Build 16.0.15831.20122 or later.
Revert to an Earlier Office Build
If you cannot immediately update to the patched version, rolling back to a previous stable Office build serves as a reliable temporary workaround.
Switch to WPS Office for a Lightweight and Reliable Experience
While WPS Office does not feature a relational database tool like Microsoft Access, it serves as a highly reliable, free, and lightweight alternative for your everyday document, spreadsheet, and presentation needs, eliminating the frequent update crashes associated with heavy productivity suites.
- 1. Download the Installer: Visit the official WPS Office website to download the free installation package for your operating system.
- 2. Install the Suite: Run the downloaded installer file and follow the straightforward on-screen instructions.
- 3. Open Your Files: Launch WPS Office and instantly open your existing Office documents to enjoy a crash-free editing experience.
Frequently Asked Questions
What causes runtime error 3709 in Microsoft Access?
Error 3709 in this scenario is caused by a documented bug introduced in specific Microsoft Office builds. The bug prevents DAO recordsets from executing UPDATE statements correctly, which often results in immediate application crashes.
Can I fix the Access crash without updating Office?
Yes. If you are unable to install the latest patched version (2211 or newer) through the standard update channel, you can resolve the crash temporarily by rolling back your Microsoft Office installation to a previous, stable build using the command prompt.
Are there alternative coding methods to avoid the DAO recordset crash?
As a temporary troubleshooting step, testing your SQL statements directly in the query view or executing the SQL via the db.Execute(sql) command may help bypass the specific DAO object methods that trigger the bug in affected Office builds.
