Calendar Control DLL on Windows 7 64 Bit

By in Uncategorized on .

I got a message like “MISSING: Microsoft Windows Common Controls 2.6.0? and I’m using 64bit Windows 7. Here are the steps I had to take to fix:

  1. Download the cab files from this knowledgebase article.
  2. Right click on the CAB file and choose 7-zip – Extract to mscomct2
  3. Open that folder and copy the two files (.ocx and .inf) to C:Windowssyswow64. Hit the “Continue” button with the admin symbol on it
  4. Start button and type ‘cmd’. Right click on the cmd entry that’s found and choose Run as Administrator
  5. In the command windows, change the directory to c:windowssyswow64
  6. Type ‘regsvr32 mscomct2.ocx’ and press enter

17 thoughts on “Calendar Control DLL on Windows 7 64 Bit

  1. Jan Karel Pieterse

    Hi Dick,

    Silly question maybe, but is this the 32 bit version of the ocx you’re instaling?
    And what Office version are you using here? Does the control work with 64 bit 2010?

  2. fzz

    7-zip? That’s not part of 64 bit versions of Windows 7, is it?

    So by implication, you consider 7-zip a necessary utility?

  3. Dick Kusleika

    JKP: Yes, 32 bit version of the ocx. Haven’t tried 64 bit Office and was told not to unless I had a compelling reason. I don’t even have a non-compelling reason, so I haven’t even sniffed it.

  4. Dick Kusleika

    Re 7-zip: Not necessary. I assume any compression utility that works on 64 bit Windows will work equally well. JustZipIt is my favorite, but it doesn’t work in 64 bit last time I tried. 7-zip is next on my list of favorites.

    I chose the words “…steps I had to take…” carefully for a good reason: I don’t completely understand the steps; I just know that I followed them and it worked. :) Not understanding all the implications means that it surely won’t work for everyone or that I glossed over something that was obvious to me but may not be to someone else. I had to go to about five websites to piece it all together, so I thought having it all in one place would be good.

  5. wlad

    Long-time reader, first-time poster. Love the site.

    I developed a tool in Excel 2003 that was in use for a whole year without issues. Then most of our users were upgraded to 2007. It took a bit of work to get the tool working in both environments, but this was donw and all seemed well. Then the other week a user complained that they were unable to use the tool. I worked out that they had had their PC re-imaged so had never had Office 2003 installed; therefore they never had mscomctl2.ocx on their system (the tool uses the datetimepicker control form this library). The simple fix would be to install the mscomctl2.ocx on the user’s PC. However, I can’t work out a way to do this as this particular user doesn’t have admin rights – also this problem is likely to occur in the future as other users trash their machines and require them to be re-built. Ideally I’d like to find an alternative to the DTPicker. I thought I’d found one in the shape of the calendar control, but surprise surprise, this too was missing from that user’s PC.

    Anyone have any ideas for alternatives to these controls, or am I missing something obvious?


  6. Dick Kusleika

    wlad: I tried to make an alternative to the DTPicker just a few weeks ago. It wasn’t even good enough to post as a failure. I would really love an alternative using built-in controls. Maybe I’ll take another shot at it.

  7. shell_l_d

    wlad: I agree, I recently edited a *.xlsm spreadsheet developed in Office 2007 & today I downloaded a trial of Office 2010, only to find that the xlsm doesn’t work – as it has 2 CalendarControls (for parameters to a Stored Procedure) which have been removed from Excel 2010 – for what good reason!!!

    Why do they have to keep removing stuff so spreadsheets are not compatible across versions… anyhow, I’d like something similar for Excel 2010 but I dont want each user to have to install a file though. Might just have to stick with a date cell & get the user to manually enter their date.

  8. wlad

    Thanks for the replies. I had been missing something obvious – simply use three pre-populated combo boxes; one each for day month and year. My app is for a European userbase so I put them in that order on the form. To prevent the user selecting an invalid date (e.g. 30th Feb) I put some code in the _change event of the month combo to validate the day. I’ll post the code when I’m back in front of my work PC.

  9. shell_l_d

    wlad, yeah I was thinking of something like that too but wasnt sure how to go about it… but I liked the simplicity of the calendar control. Month Day Year combo boxes & filter day based on month (eg: if select Feb only show 1 to 29)… but if feb29 selected would have to validate year or maybe just populate it with leap years. Still learning stuff lol. :)

  10. shell_l_d

    Related posts:

    * Date/Time/Calendar Control to work in multi Excel platforms (2003/2007/2010)?

    * Problem with Date/Time Picker in Excel 2000

    * Multi-compatible Excel xlsm – how to solve object/activex/reference issues:

    * Excel – Date & Time Picker / Calendar Controls – multi compatible ???

    * Calendar Control DLL on Windows 7 64 Bit

  11. Pingback: Win 7 64 and Calendar Control

  12. Pingback: Please Can You Help With A Calendar Date Picker In 2010

Leave a Reply

Your email address will not be published. Required fields are marked *

To create code blocks or other preformatted text, indent by four spaces:

    This will be displayed in a monospaced font. The first four 
    spaces will be stripped off, but all other whitespace
    will be preserved.
    Markdown is turned off in code blocks:
     [This is not a link](

To create not a block, but an inline code span, use backticks:

Here is some inline `code`.

For more help see