I have seen 3 reports today alone of version 2506 causing issues with Access, so be forewarned.
Now, this is very early reporting and there could always be other factors at play, but I’ve seen several reports of issues with Access database since upgrading to Version 2506. Issues like:
- Access taking very long to close (upward of 2 minutes)
- Macros don’t show when trying to import them into another database
- When looking up macro in a form control expression Chinese characters appear
As always, if after any update you start facing issues/bugs, then the solution is quite simple:
- Rollback your installation to a prior build
- Disable Office Automatic Updates
- Wait for the storm to pass and Microsoft to release a fix (this can take days, weeks, months or even longer in some cases)
I’m going to end with what I replied to someone facing such an issue in one of the online forums:
You’ve got to expect issues when you run Insiders/Beta, Preview or Current update channels!
I’ve always recommend my clients switch to semi-annual for stability (at least as much stability as you can get with Microsoft products!).
If you’re running 2506 and experiencing issues, please drop me a comment below indication the issue you seem to be experiencing.
Thanks for this.
A suggestion: Please add a date to your posts. When I first read it, I wasn’t sure if 2506 was a recent version or if this was an old post referring to an older version. A date added to your posts would immediately let me know if this was a new or current issue.
Thanks. 🙂
With regards to knowing if a version is recent or not, just look at the Version No itself:
2506
25 => 2025
06 => June
so you know it’s a recent issue. You can also simply consult: Update history for Microsoft 365 Apps (listed by date)
As for dates, I used to have them but removed them as Google penalizes blogs of having them.
I never realized that Google penalizes for blog post dates. Interesting. 🙂
As for the update history, I am not a fan. I noticed that my MSACCESS.exe file gets a new date and time stamp every time a new 365 update is pushed, but Microsoft’s update history hardly ever lists what has changed in the newer version. That drives me crazy. Case in point, all these new issues in 2506 and not a mention of anything being done to Access in the update history (no bug fixes or features). The last time Access was mentioned in their update history was for version 2503 back in April 🙁
Yes, I’ve posted about this a couple times. Sadly, the Access Dev Team does not usually provide Release Notes. So although updates were made, as you correctly mentioned, there is no indication of this so user are made aware of what changes occurred. I’ve brought this up, but no change in behavior has ever occurred.
Some will say they post some of that on their blog page. Yes and No, firstly there have been posting lapses on their blog. Also, that simply is not the place for such information. That information belong in the Release Notes provided on the update page! That’s where users go to lookup version/build information, that where such information need to be centrally accessible.
“As for dates, I used to have them but removed them as Google penalizes blogs of having them.”
What is the logic behind THAT?!?
I had come across some articles/videos explaining Google viewed information as stale based on dates.
So more recent article seem to indicate Google has since adapted their algorithm. I have to do more research. One way or another, with AI, my blog (all blogs and forums in reality) have seen a massive decrease in traffic.
I also noticed another issue in 2506, the Date Picker control that appears when someone selects it next to a date text field no longer functions correctly.
It allows someone to select a date, but the chosen date doesn’t automatically get entered back into the date field.
I was able to duplicate this issue on all of my forms under 2506.
Rolled back to 2505 as my users were randomly getting #Name? in all the form fields specifically if they were on a form and left there desk for awhile then returned after 10min or more forcing them to either reload the form or reload the program. didn’t have this issues till a few days ago possibly end of last week.
This above issue is confirmed NOT to be part of the 2506 build of Office. Instead it was caused but a completely unrelated issue and has since been resolved. I would have deleted the above, and hope the moderator might do so, as to not steer someone in the wrong direction. Thank you
Thank you for sharing this information.