Can't exit design mode because Control 'xxxx' can not 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.
microsoft-excel microsoft-excel-2010
add a comment |
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.
microsoft-excel microsoft-excel-2010
Maybe a stupid suggestion, but have you tried deleting and then recreating the control?
– Excellll
Jan 8 '15 at 18:36
There are many controls; if I delete the one, the same issue occurs with the next. I suppose I could delete them all and start over from scratch.
– Jean-François Corbett
Jan 8 '15 at 21:54
1
OMG I'm getting old... I answered this very same question myself 8 months earlier!!
– Jean-François Corbett
Jan 20 '15 at 8:06
add a comment |
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.
microsoft-excel microsoft-excel-2010
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.
microsoft-excel microsoft-excel-2010
microsoft-excel microsoft-excel-2010
edited May 23 '17 at 12:41
Community♦
1
1
asked Jan 8 '15 at 9:14
Jean-François Corbett
1,95921624
1,95921624
Maybe a stupid suggestion, but have you tried deleting and then recreating the control?
– Excellll
Jan 8 '15 at 18:36
There are many controls; if I delete the one, the same issue occurs with the next. I suppose I could delete them all and start over from scratch.
– Jean-François Corbett
Jan 8 '15 at 21:54
1
OMG I'm getting old... I answered this very same question myself 8 months earlier!!
– Jean-François Corbett
Jan 20 '15 at 8:06
add a comment |
Maybe a stupid suggestion, but have you tried deleting and then recreating the control?
– Excellll
Jan 8 '15 at 18:36
There are many controls; if I delete the one, the same issue occurs with the next. I suppose I could delete them all and start over from scratch.
– Jean-François Corbett
Jan 8 '15 at 21:54
1
OMG I'm getting old... I answered this very same question myself 8 months earlier!!
– Jean-François Corbett
Jan 20 '15 at 8:06
Maybe a stupid suggestion, but have you tried deleting and then recreating the control?
– Excellll
Jan 8 '15 at 18:36
Maybe a stupid suggestion, but have you tried deleting and then recreating the control?
– Excellll
Jan 8 '15 at 18:36
There are many controls; if I delete the one, the same issue occurs with the next. I suppose I could delete them all and start over from scratch.
– Jean-François Corbett
Jan 8 '15 at 21:54
There are many controls; if I delete the one, the same issue occurs with the next. I suppose I could delete them all and start over from scratch.
– Jean-François Corbett
Jan 8 '15 at 21:54
1
1
OMG I'm getting old... I answered this very same question myself 8 months earlier!!
– Jean-François Corbett
Jan 20 '15 at 8:06
OMG I'm getting old... I answered this very same question myself 8 months earlier!!
– Jean-François Corbett
Jan 20 '15 at 8:06
add a comment |
3 Answers
3
active
oldest
votes
There is a very simple fix for this issue:
- Close all Excel documents
- Open a blank document
- Excel options > Trust center settings>macro settings>Select{Disable all macros with notifications}
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.
add a comment |
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,
add a comment |
Due to a recent Office Update, ActiveX Controls became useless, maybe that's the issue that troubles you.
There ara a few archives related that once deleted and regenerated can solve your problem, if that's your issue.
For more information, you can read this post:
Bacon Bits: Office Update Breaks ActiveX Controls
Hope it works!
While this link may answer the question, it is better to include the essential parts of the answer here and provide the link for reference. Link-only answers can become invalid if the linked page changes.
– DavidPostill♦
Jan 8 '15 at 13:22
You're right. I've already edited it.
– Angel
Jan 8 '15 at 13:38
No, this is a different issue.
– Jean-François Corbett
Jan 8 '15 at 18:27
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f862168%2fcant-exit-design-mode-because-control-xxxx-can-not-be-created%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
3 Answers
3
active
oldest
votes
3 Answers
3
active
oldest
votes
active
oldest
votes
active
oldest
votes
There is a very simple fix for this issue:
- Close all Excel documents
- Open a blank document
- Excel options > Trust center settings>macro settings>Select{Disable all macros with notifications}
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.
add a comment |
There is a very simple fix for this issue:
- Close all Excel documents
- Open a blank document
- Excel options > Trust center settings>macro settings>Select{Disable all macros with notifications}
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.
add a comment |
There is a very simple fix for this issue:
- Close all Excel documents
- Open a blank document
- Excel options > Trust center settings>macro settings>Select{Disable all macros with notifications}
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.
There is a very simple fix for this issue:
- Close all Excel documents
- Open a blank document
- Excel options > Trust center settings>macro settings>Select{Disable all macros with notifications}
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.
edited Aug 15 '15 at 6:57
Jamal
4561617
4561617
answered Aug 15 '15 at 1:19
Sujith Srinivas
1
1
add a comment |
add a comment |
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,
add a comment |
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,
add a comment |
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,
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 '15 at 11:53
JoeBloggs
1
1
add a comment |
add a comment |
Due to a recent Office Update, ActiveX Controls became useless, maybe that's the issue that troubles you.
There ara a few archives related that once deleted and regenerated can solve your problem, if that's your issue.
For more information, you can read this post:
Bacon Bits: Office Update Breaks ActiveX Controls
Hope it works!
While this link may answer the question, it is better to include the essential parts of the answer here and provide the link for reference. Link-only answers can become invalid if the linked page changes.
– DavidPostill♦
Jan 8 '15 at 13:22
You're right. I've already edited it.
– Angel
Jan 8 '15 at 13:38
No, this is a different issue.
– Jean-François Corbett
Jan 8 '15 at 18:27
add a comment |
Due to a recent Office Update, ActiveX Controls became useless, maybe that's the issue that troubles you.
There ara a few archives related that once deleted and regenerated can solve your problem, if that's your issue.
For more information, you can read this post:
Bacon Bits: Office Update Breaks ActiveX Controls
Hope it works!
While this link may answer the question, it is better to include the essential parts of the answer here and provide the link for reference. Link-only answers can become invalid if the linked page changes.
– DavidPostill♦
Jan 8 '15 at 13:22
You're right. I've already edited it.
– Angel
Jan 8 '15 at 13:38
No, this is a different issue.
– Jean-François Corbett
Jan 8 '15 at 18:27
add a comment |
Due to a recent Office Update, ActiveX Controls became useless, maybe that's the issue that troubles you.
There ara a few archives related that once deleted and regenerated can solve your problem, if that's your issue.
For more information, you can read this post:
Bacon Bits: Office Update Breaks ActiveX Controls
Hope it works!
Due to a recent Office Update, ActiveX Controls became useless, maybe that's the issue that troubles you.
There ara a few archives related that once deleted and regenerated can solve your problem, if that's your issue.
For more information, you can read this post:
Bacon Bits: Office Update Breaks ActiveX Controls
Hope it works!
edited Jan 8 '15 at 13:36
answered Jan 8 '15 at 12:31
Angel
262
262
While this link may answer the question, it is better to include the essential parts of the answer here and provide the link for reference. Link-only answers can become invalid if the linked page changes.
– DavidPostill♦
Jan 8 '15 at 13:22
You're right. I've already edited it.
– Angel
Jan 8 '15 at 13:38
No, this is a different issue.
– Jean-François Corbett
Jan 8 '15 at 18:27
add a comment |
While this link may answer the question, it is better to include the essential parts of the answer here and provide the link for reference. Link-only answers can become invalid if the linked page changes.
– DavidPostill♦
Jan 8 '15 at 13:22
You're right. I've already edited it.
– Angel
Jan 8 '15 at 13:38
No, this is a different issue.
– Jean-François Corbett
Jan 8 '15 at 18:27
While this link may answer the question, it is better to include the essential parts of the answer here and provide the link for reference. Link-only answers can become invalid if the linked page changes.
– DavidPostill♦
Jan 8 '15 at 13:22
While this link may answer the question, it is better to include the essential parts of the answer here and provide the link for reference. Link-only answers can become invalid if the linked page changes.
– DavidPostill♦
Jan 8 '15 at 13:22
You're right. I've already edited it.
– Angel
Jan 8 '15 at 13:38
You're right. I've already edited it.
– Angel
Jan 8 '15 at 13:38
No, this is a different issue.
– Jean-François Corbett
Jan 8 '15 at 18:27
No, this is a different issue.
– Jean-François Corbett
Jan 8 '15 at 18:27
add a comment |
Thanks for contributing an answer to Super User!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f862168%2fcant-exit-design-mode-because-control-xxxx-can-not-be-created%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Maybe a stupid suggestion, but have you tried deleting and then recreating the control?
– Excellll
Jan 8 '15 at 18:36
There are many controls; if I delete the one, the same issue occurs with the next. I suppose I could delete them all and start over from scratch.
– Jean-François Corbett
Jan 8 '15 at 21:54
1
OMG I'm getting old... I answered this very same question myself 8 months earlier!!
– Jean-François Corbett
Jan 20 '15 at 8:06