Geek Answers Handbook

Corrupt ActiveX Control? "Cannot exit development mode because" DTPicker1 "cannot be created."

I am developing an Excel VBA application on my desktop computer. I have a DatePicker ActiveX control on my spreadsheet. It worked fine.

Then, during the trip, I worked on a laptop application. When I returned, I moved the file back to my desktop computer. Now, when I try to start the application, I constantly get the error message "Unable to exit development mode, because Control" DTPicker1 "cannot be created."

Renaming the control and all its links in the code did not help. When I try to remove a control, I still get a message, even if the control of this name is no longer controlled.

How to fix it?

+7
vba excel activexobject
source share
3 answers

Something in your book seems to be corrupt. Something similar happened to me once or twice.

The solution is to copy everything (the contents of the code and the sheet) into a new book and restore your application there.

[Updated with comment, as this solved the problem.]

+6
source share

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

After some online investigation, I found a little complicated guide on how to solve the problem:

  • Open the project code and upload the links that Excel allows.
  • Make a small change in your code (I added one line of comments) - reload the project or something like that.
  • Run a macro, for example, only the one that activates the first sheet.
  • Close and reopen Excel.
  • Voila - Date and time collectors load correctly.

As the first one, I deleted temporary files in "C: \ Users \ xxx \ AppData \ Local \ Temp \ Excel8.0", but this did not help as a separate action, so I do not know if this is a useful action or not.

+1
source share

Had a similar problem when the “Control” CommandButton13 could not be created. ”The spreadsheet was still working on my colleagues computer. I noticed in the VBA editor that Sheet13 was renamed CommandButton1. On my colleagues computer, we changed the name to Sheet13. Now it works fine on my pc.

0
source share

More articles:


All Articles