H
Harald Staff
I have written some programs in VB6 using a few OCX controls (MSCOMCTL.OCX, MSCOMCT2.OCX and a few others. Standard MS things).
Those are included in the Setup files.
One of my users get the error message "MSCOMCTL.OCX or one of its dependencies are not properly registered" when the application is
attempted started. Another user, running the very same file on the very same computer, has no problems running the app.
Now here comes the weirdest part: Rightclicking the ocx file in windows explorer, system32, "properties", shows several tabs of
information; company Microsoft, build number, build date and all the usual things for signed files. The unlucky user sees all this
too on mscomct2, but no such things on mscomctl. That one looks like an unknown file from an unknown source. It is not, as the other
profiles proves.
Now what could possibly cause a thing like this ?
Best wishes Harald
Excel MVP
Those are included in the Setup files.
One of my users get the error message "MSCOMCTL.OCX or one of its dependencies are not properly registered" when the application is
attempted started. Another user, running the very same file on the very same computer, has no problems running the app.
Now here comes the weirdest part: Rightclicking the ocx file in windows explorer, system32, "properties", shows several tabs of
information; company Microsoft, build number, build date and all the usual things for signed files. The unlucky user sees all this
too on mscomct2, but no such things on mscomctl. That one looks like an unknown file from an unknown source. It is not, as the other
profiles proves.
Now what could possibly cause a thing like this ?
Best wishes Harald
Excel MVP