Dependency info out of date for mscomctl.ocx

I have this same problem please Swift if you have fixed it let me know how?? anyone else if you know how to fix this problem please please let me know

Tom



Hi all,

I was hoping someone might have run into this before. When I package my project using the PDW, it tells me that the dependency information for mscomctl.ocx is out of date. It asks me whether I want to proceed anyway, which I do, but then I find that after installing my program on another box and running it, the Office 2000 installer starts up, ready to install some ocx or dll maybe that I still need to run the program. I have worked on this for a while now, and I have no answers left.

I am using VB6 Enterprise on a Win2000 Professional box. I am installing it on a 2000 Professional box as well. My mscomctl.ocx is version 6.1.83.41.

I originally thought that my status bar or progress thermometer was causing windows to want to install something off the office cd, but the funny thing is that if I cancel the office 2000 install box that pops up when I run the program, it still runs fine - in other words, the status bar, and progress thermometer (and data environment and reports) come up just fine anyway! Still, the install box is annoying and unprofessional.

Does anyone have any suggestions?

Swift

I'm exactly in the same situation but don't have this problem.
Try to package that ocx together with your program as not-shared and have the control be copied in the AppDir. This is what I'm doing with every dll/ocx that my apps use and I'm very satisfied with the results.

Bob,
I tried what youo said and I still get the installer to pop up. If you could try this and see if it happens to you I would be very grateful.

create a quick vb6 program, just put a couple of controls for windows components 6.0 (mscomctl.ocx) on it (imaglist,tree view). Make a install program (install shield or package wizard)


on a win2000 or XP machine that has office 2000 installed. install the program you just created.

now creat another user or switch to another user and run the program...do you get this installer to popup???


thanks Tom



I'm exactly in the same situation but don't have this problem.
Try to package that ocx together with your program as not-shared and have the control be copied in the AppDir. This is what I'm doing with every dll/ocx that my apps use and I'm very satisfied with the results.

Ooh, I have Win98 single user; so I can't: that means I'm not comparable to you.

I had this problem with the OCX as well and have found that a newer MSCOMCTL.OCX exists with version 6.0.88.62. I believe this version comes with VB6 SP5.

When installing a selfcreated program using Wise, Windows 2000 ran into problems with the older 6.1.83.41. It asked for the Windows 2000 CD to correct the problem, but that did not help. The problem with this seems to be that it is not a Windows 2000 file, but an Office file. That is probably why the Office Installer message can appear.

I think replacing the other (to my opinion incorrectly versioned) with the 6.0.88.62 version corrects the problem. It did for me.