>I was having a problem with using msacal70.ocx in my application...on some machines the calendar control would be black and unreadable. We then switched to using mscal.ocx, which is version 8 I believe. Everything worked fine until we tried running the setup on a new machine. We now get the error "Mscal.ocx was not able to register itself in the system registry". I am not sure what I need to change to fix this error.
>
>This file was added to the setup wizard and was checked as an activeX control.
>
>Any ideas?
>

In addition to being unable to register, there's usually an obscure hexadecimal number that gives some clue as to what caused the problem. I suspect that one or more of the supporting .DLLs used by the .OCX either were an older version than the .DLL needed (a later version might have a different set of entrypoints that the OCX relies on) or that some other component needed to be registered before the OCX, so that its registry entries were available when the OCX tried to register itself (I've seen this when trying to register an OCX that depended on an ODBC component's registration information; ensure that ODBC installed first fixed the problem for me in that case. I'm not aware of that kind of dependency for the MSCAL control.)

>Thanks,
>Paul