Fix Microsoft Access Saving Only Part of a Record After Microsoft 365 Update
Question details
Users need to resolve a bug where Microsoft Access fails to save complete transaction records and returns Null results on DLookup queries after an Office update.

- Product
- Microsoft Access (Microsoft 365)
- Device & OS
- Windows 11
- Scenario
- Running long-running database applications, saving transaction fields, or performing data retrieval queries after updating Microsoft 365.
- Observed behavior
- The application saves only some transaction fields. Values appear during debugging but later queries return blank or Null results. Background processes may remain open upon exit.
Verify your current Microsoft 365 version by opening Access, clicking on File > Account, and checking the About section to see if your system is running the problematic version 2408.
Update Microsoft 365 Apps to Version 2409
Updating to the latest version of Microsoft 365 resolves the data truncation and DLookup bugs introduced in version 2408.
Microsoft has acknowledged the partial record save issue that surfaced in the 2408 build. Applying the version 2409 patch directly fixes the query handling and transaction saving mechanics without requiring complex database modifications.
Launch Microsoft Access or any other Microsoft 365 application. Click on 'File' in the top left corner of the screen and select 'Account' from the left-hand menu.
Under the 'Product Information' section, locate the 'Update Options' drop-down button and click on it.
Select 'Update Now'. The system will check for available patches and download version 2409 or later. Wait for the process to complete.
Once the update is installed, restart your computer and run your Access application to confirm that complete records are now being saved.

Roll Back Office Using the Office Deployment Tool
If the 2409 update introduces new startup errors, rolling back to an older, stable release like 2407 is the best workaround.
Correct Windows 11 Regional Date Settings
Fix date-format mismatch issues that can cause database queries to fail after a Windows 11 feature upgrade.
Switch to WPS Office for a Stable, Bug-Free Experience
Microsoft Access issues often stem from complex, interconnected Office updates that unexpectedly break essential features. While WPS Office does not include a direct relational database application, it provides highly stable, robust, and free alternatives for Word, Excel, and PowerPoint without the heavy update bugs. Use WPS Spreadsheets to reliably manage, filter, and analyze your tabular data.
- 1. Download the installer: Visit the official WPS Office website and click the free download button.
- 2. Install WPS Office: Run the lightweight setup file and follow the quick on-screen instructions.
- 3. Open and analyze your data: Launch WPS Spreadsheets to import your existing data sets and manage them securely without missing records.

Frequently Asked Questions
Why does Microsoft Access stay open in the background after I close it?
This 'ghost process' issue frequently happens when VBA code encounters an unhandled error, a database object isn't properly closed (set to Nothing), or due to the specific bug introduced in Microsoft 365 version 2408. You can temporarily fix it by manually ending the 'MSACCESS.EXE' process in the Windows Task Manager.
How can I check which version of Microsoft 365 I am currently running?
Open any Microsoft Office application, click on 'File', and select 'Account'. Look under the 'Product Information' section; the version and specific build number will be displayed next to the 'About' button.
Why are my DLookup functions suddenly returning Null values?
DLookup returns Null if the targeted data is genuinely missing, if the criteria formatting (like dates) conflicts with system settings, or due to a known bug in Access version 2408 where the application fails to properly commit saved transaction data to the table.
Can a Windows update actually change my system date format?
Yes, major Windows feature updates (such as upgrading Windows 11 from version 22H2 to 23H2) can sometimes inadvertently reset regional settings. This disrupts database applications that are hardcoded to rely on a specific date format, such as DD/MM/YYYY.




