Ошибка can t design mode because control can t be created

What is the cause of this error and how do I fix it?

This started occurring on a workbook of ours for reasons unexplained. I made a tiny change to the VBA code behind it, just plotting slightly different values on a chart; everything looks really benign, and definitely not button-related. Why this error, then?

The error occurs only on certain machines, not others.

There is a Microsoft Dev Center article on this error, but it isn’t helpful:

All controls must be instantiated before you can exit design mode. This error has the following causes and solutions:

The control specified in the error message dialog box could not be created. Code can only run after all controls are instantiated and properly connected. Make sure every file needed for the control is available before trying again.

Note that this is a different issue from the one caused by the Dec 10, 2014 Microsoft Office automatic update; the fix for that one doesn’t solve this problem.

There is a very simple fix for this issue:

1. Close all Excel documents
2. Open a blank document
3. Excel options > Trust center settings>macro settings>Select{Disable all macros with notifications}

4. Active X settings >

   Select either:

   • Disable all controls without notifications
   • Prompt me before enabling all controls with minimal restrictions

Apply all settings and close.

Open the affected file and check allow the prompt to enable macros if required.

I had the same message for Control ‘CommandButton13’. The spreadsheet worked OK on my colleagues PC, but not mine.
I noticed that in the VBA editor, one of the worksheets had somehow had the name changed from Sheet13 to CommandButton1. On my colleauges PC, we changed the name back & saved the file. It now works OK on my PC too.

Cheers,

answered Sep 21, 2015 at 11:53

My answer to the problem was to delete the control buttons from the errored file and then just copy/paste the original ones back in from a previous copy of the file. It seemed to work fine.

I am developing an Excel VBA application on my desktop machine. I have a DatePicker ActiveX control on my spreadsheet. It was working fine.

Then, while on travel, I was working on the application on a laptop. When I returned, I moved the file back to my desktop machine. Now when I try to run the app, I continually get the error «Can’t exit design mode because Control ‘DTPicker1″ can not be created».

Renaming the control and all its references in the code hasn’t helped. When I try to delete the control I still get the message even though there is no longer a control of that name.

How do I fix this?

In my case, an error occurred when I developed an excel sheet with ActiveX DTPicker control in MS Excel 2013, moved it to Excel 2010 (still working), saved some changes and moved it back to the development environment in Excel 2013 — DTPickers cannot be loaded.

After some internet investigation I found a bit tricky manual how to solve the issue:

1. Open the project code and unload the References that Excel allows.
2. Make some little change in your code (I added one comment line) — to reload the project or something like that.
3. Run some macro, for example only the one activating the first sheet.
4. Close and reopen the Excel.
5. Voila — Date and time pickers are loaded correctly.

As a firs I deleted the temporary files in «C:UsersxxxAppDataLocalTempExcel8.0» but it did not helped as a standalone action, so I don’t know, if it is a useful action or not.

answered Feb 25, 2015 at 17:01

answered Sep 21, 2015 at 11:58

Years later, stumbled on a solution, only because I recorded the steps that led up to the situation.

1) Had changed all worksheet securities to include UserInterfaceOnly:= True
2) Active-X controls were on protected sheets

The Workbook:Open included a routine to refresh all the sheet protections, something needed for UserInterfaceOnly to work, allowing macros to make sheet changes, but not the user. Always the newest Active-X control gave the ‘Can’t Exit Design Mode because…» or if the project is protected altogether, a 57121 error, which is catastrophic if trying to switch the offered Debug mode. Saving the workbook with the sheet that has the newest AC on it and reopening gave no issue.

Solution: Copied the protection loop at bottom to the top of Workbook_Open and changed protect to unprotect password(whatever yours is). Now the workbooks open again without any of these 2 warnings. Added the protection loop also to the Before_Safe to ensure the workbook would always be in a secure state, in case it gets loaded on a macro disabled system.

answered Jan 18, 2020 at 11:36