ActiveX control registration problem

[David Moerman]

Hello all,
I have an application that uses Microsoft's "Date & Time Picker" control which is located in MSCOMCT2.OCX. My development platform was Win2000 with Office 2000 and VC++6.0 installed. When I tried to register this OCX file (using "regsvr32 MSCOMCT2.OCX") on another Win2000 machine (but has Office 97, no Visual C++) I received no error, and the control appears on the ActiveX pick list, but the container remains empty. Further, when I tried to add the control to a MS-Access 97 form (essentially a VB form), I got the error message "OLE Server isn't registered". This gave me a hint that the regsvr32 actually didn't work, but I have no idea why not. Is this telling me that MSCOMCT2.OCX is not redistributable? I searched Mic
rosoft's website for a couple hours and didn't find anything that said I couldn't redistribute this OCX file. What gives?

[drval]

I've had trouble with OCXs that called other OCxs. I don't know if this relates but if it does, it can be very, very tricky to get those calls to work well.

I've also seen cases where it was necessary to regsvr32 /u and then regsvr32 the OCX several times, including reboots even, before the registration actually "worked"....My experience is that these problems are exacerbated when the OCX was generated using VB.

[David Moerman]

Yes, I've discovered that there are ".DEP" or dependancy files that go along with these OCXs. In the MSCOMCT2.DEP we find that it "Uses1=ComCat.dll". I've verified that this exists. No joy.

Also, I discovered in the MSDN library that after Visual Basic 5.X the controls within COMCTL32.OCX and COMCT232.OCX were updated by MSCOMCTL.OCX and MSCOMCT2.OCX respectively. On my machine that works, all 4 files seem to be registered. I ensured that all 4 files were also registered on the target machine, just in case they were somehow "linked". Still no joy.