Wizard ActiveXs are Broken in 32 Bit (Fixed)
- Karl Donaubauer
- Aug 12
- 2 min read
Updated: Aug 22
Description
Since version 2507 build 19029.20136 from July 30 some wizards in 32 bit versions of Access throw error messages like this: "The expression XYZ you entered as the event property setting produced the following error: There was an error loading an ActiveX control on one of your forms or reports." (where XYZ is the name of an event in the ActiveX)
As of this writing, it affects Current, Current Preview, and Beta channels. 64 bit versions are not affected.
Examples where the problems occur:
External Data - Import and Link - Text File and Excel
When you select a column in the Field Options dialog, it throws this message:
In the text file import dialog to set the column widths of fixed width text files:
You can then continue the process, but the involved functionalities are not available, which may negatively affect the result of the import or link process.
Database Tools - Analyze - Database Documenter+Analyze Performance
Error messages like this are displayed when you open a dialog, move the mouse over it or click on it:
Forum discussions:
This Microsoft TechCommunity thread where linked objects are not visible in the old Linked Table Manager in Access 2016 MSI shows another negative effect of the bug.
Status
Microsoft has released a bugfix in the Current Channel version 2507 build 19029.20208 from August 19.
If you do not receive it automatically, you can retrieve it by choosing File – Account – Update Options – Update Now.
Workaround 1
A temporary remedy is to roll back to an older build of Office/Access in which the bug does not yet occur, i.e. earlier than 19029.20136.
Workaround 2
If you continue the wizard process despite the error messages you can then try to correct the settings that were not made due to the bug afterwards in the (e.g. import/link) result.
Same error when using the old “Web Browser control” that you insert from ActiveX controls. If you go to security settings and enable ActiveX controls it works. But that looks bad at customer sites. So we went through every program and changed it out for the native control. Took some work, and it has had its challenges. Still fighting some issues. But it may be the best option in some cases. If you trust the ActiveX in your program, and it isn’t used anywhere outside your organization, it might be worth just enabling the controls. Hopefully this fix comes out and everyone is spared the issue.