Hi Mohammad, Please follow the steps below: >>Click on the link given below that will download the MSCOMCT2.cab Download MSCOMCT2.cab Open MSCOMCT2.cab file then you will see 2 files. Copy MSCOMCT2.OCX file and paste it in C: Windows System32. Open Excel Go to “Developer” Tab. Click on “Insert” in “Controls” group.

Click on “More Controls” Then click on “Register Custom” Button. Shejr dar borai modar padar lyrics. Then in C: Windows System32 find the “MSCOMCT2.cab” and click on “ok” button.

You're correct that this is really painful to hand out to others, but if you have to, this is how you do it. Just extract the.ocx file from the.cab file (it is similar to a zip).

Now you can see it in a list of additional tools for the userform Source: _____________________________________________________________________________________ Power to the Developer! Dell Precision M6800 - 17.3', Core i7, 16GB RAM, nVIdia Quadro, 128GB SSD, 1TB HDD.

We use a calendar control as part of several MS Access 2007 databases. This is not a problem in Windows XP, but we are migrating to 64 bit Windows 7 and are having trouble registering this OCX control under this OS.

We've tried running as administrator, both from a shortcut and from a command prompt. We've also tried logging into the machine as a local admin - none of these works. The error when failing is 0x8002801C. I've read that Microsoft is possibly fazing out support for VB6 controls in the 64 bit version of Windows 7 but have heard nothing definite. If there is an alternative to using this control that would still work with Access 2007 and run under Windows 7, I'm willing to give that a try. Office 2010 is not out yet so there must be something that will work in the interim.

Hi OfficeBoy48, We have just had the same problem and have now worked out how to do it. You need to copy the MSCOMCT2.OCX file to c: windows sysWOW64 not c: windows system32. You then can register it by running from the command prompt or run in the start menu regsvr32 c: windows sysWOW64 mscomct2.ocx and it should register although make sure that you run regsvr32 with administrator privileges. Please note, if you try to register the ocx from c: windows system32 using regsvr32 you will get the following error: The module “c: windows system32 mscomct2ocx” failed to load. Make sure the binary is stored at the specified path or debug it to check for problems with the binary or dependent.DLL files.

The specified module could not be found. We think this is because windows 64 bit is mucking about with what directories it is reporting to the regsvr32 although this is just our educated guess. If you need an up to date version of mscomct2.ocx you can get it from Good luck Rod.