there is no object in this control

Question

I have an Access 2013 accde file which has references to the MSCOMCTL library for ListViews and other "activeX" controls. This past week, the application began to fail for computers that had Access 2016 installed. The error given is 2683 There is no object in this control.

Upon further investigation, it appears that a Microsoft Update released on or around August 1 is causing this issue.

I tried opening the original accdb file in Access 2016 and receive the same error. Looking at the design of a form that has the ListView, I cannot access the ListView Properties.

I also tried the following to no avail:

• Manually unregistering and registering the mscomctl file.
• De-compiling the Access Database and recompiling it.
• Checked for missing and broken references

This is only an issue in Access 2016. When opening up the file in Access 2013 there is no problem.

I have hundreds of users and this behavior is consistent for everyone using Access 2016 (and only began this past week) in different environments. Access 2013 users have no issue at all.

Any help would be greatly appreciated.

Answer 1

I'd be looking to uninstall (or as Microsoft is now calling it, revert) the recent update (the recent updates have been causing all sorts of headaches, so be very careful before implementing them - you'll need to start testing them yourself as MS seems not to be doing it anymore), see:

https://support.microsoft.com/en-ca/help/2770432/how-to-revert-to-an-earlier-version-of-office-2013-or-office-2016-clic

https://www.cnet.com/how-to/how-to-revert-to-the-previous-version-of-office-365/

---

Daniel Pineault, 2010-2017 Microsoft MVP
Professional Support: http://www.cardaconsultants.com
MS Access Tips and Code Samples: http://www.devhut.net

Answer 2

Hello,

What is your Office 2016 build number?  I test in 1707 8326.2070, the ListView is working. Please update to the latest version to check if your issue is fixed. Please visit  Version and build numbers of update channel releases to check the latest version for different update channel.

Regards,

Celeste

---

MSDN Community Support
Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact [e-mail].

Answer 3

Uninstalling or reverting is obviously not a solution, especially as I'm dealing with hundreds of clients using the Access app...

Answer 4

I'm not sure how to check the "Build" on my computer, but I do see that the version is 16.0.4549.1000 (under File > Account > About Access).

In Programs and Features, the version reads 16.0.4266.1001. (not sure why the difference).

To clarify the issue: There is no problem in using Access's ListView control. It is the MS Common Controls (ListView) that is the issue. It is also not a problem using Access 2016 and the ListView control; it is only an issue with an accde file created using Access 2013. 

Finally, this issue only just came up, apparently due to Office Updates. It is affecting hundreds of users of the app (accde file) already in production.

Answer 5

Sadly, at present, I believe (I could be wrong) it is the only solution.  Your other option is to way for the next update in the hopes it rectifies whatever has gone awry.

Good luck either way, this stuff is very frustrating to say the least!

---

Daniel Pineault, 2010-2017 Microsoft MVP
Professional Support: http://www.cardaconsultants.com
MS Access Tips and Code Samples: http://www.devhut.net

Answer 6

Daniel,

Is this issue officially recognized and confirm by Microsoft as a bug? Is there a KB about it?

And if yes, do you know if there is a timeline or estimate as to when it will be fixed?

Thanks

Answer 7

I've never seen KB article for bugs and I haven't heard anything officially from MS on this.  I saw another thread about this and the conclusion was it was related to an update because the issue went away when they referred their installation.  That's why I recommended you try it as well in the hopes it would work for you to.  You could try it with one or two clients just to confirm and then go from there.

---

Daniel Pineault, 2010-2017 Microsoft MVP
Professional Support: http://www.cardaconsultants.com
MS Access Tips and Code Samples: http://www.devhut.net

Answer 8

Hello,

If I create db and insert controls in Access 2016 and then open in Access2013, i could get the error "There is no object in this control". If you insert the built-in ListView control in Access 2016 and then open the db in 2013, would you get the same error? It seems that the MSCOMCTL.OCX doesn't work both for Access 2013/2016 after updates. 

Recently, several customers report issues when using MSCOMCTL.OCX after updating, please try to uninstall KB4011051 to check if your issue could be fixed. Besides, please submit a feedback by File -> Feedback.

https://social.technet.microsoft.com/Forums/office/en-US/bda97d87-a41d-47a0-b55d-6db43d616db6/license-check-bug-in-latest-update-to-access-2016-activex?forum=Office2016ITPro

https://social.technet.microsoft.com/Forums/office/en-US/01122b02-f82a-40dc-b7ab-341b0a5790e2/latest-office-update-for-2016-seems-to-have-broken-tabctl32ocx?forum=excel

https://social.technet.microsoft.com/Forums/office/en-US/e642eac3-e842-4f5b-a774-5516b9bf8474/aug-1-office-update-kb4011051destroys-wmi-access-from-excel?forum=excel

https://social.msdn.microsoft.com/Forums/office/en-US/d3847258-16b9-4956-8bff-0a70c80b1ca7/error-429-in-office2016office365-version-1707?forum=exceldev

Regards,

Celeste 

---

MSDN Community Support
Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact [e-mail].

Answer 9

Can confirm. I am using 2016, but the .accdb file is from 2010. The update broke everything that involved ListViews from the MSComCtl.ocx file. Uninstalling update KB4011051 corrected the issue.

Answer 10

Hello,

The issue has been fixed by recent updates.

Please install KB4011093 if you are using MSI package.

https://support.microsoft.com/en-us/help/4011093/august-22-2017-update-for-office-2016-kb4011093

If you are using C2R, please update to the latest Version 1707 build 8326.2087.

Regards,

Celeste

---

MSDN Community Support
Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact [e-mail].