MSCOMCTL.OCX out of date

  • Thread starter Thread starter Garry
  • Start date Start date
G

Garry

On my machines, MSCOMCTL.OCX is version 6.0.88.62. On another machine it
is 6.1.95.45.

How can I get all my ocx / dll files in system32 upto date.

windowsupdate is fully upto date, and I use VB6.0 sp5.

Any ideas please, as this is effecting my VB6 apps. (I use package &depoly
to make software release. When I go to a client running NT4, sp6, my install
gives a message that many of the ocx/dll files on my CD are older then those
onthe client pc!). My software then fails on the pc. I think my development
pc needs to be updated.

any ideas please


garry
 
Doug

thanks for yor replay.

I was not aware if this DLL database - very useful.

I still however, have a problem.

I have a VB app which until last week worked fine on my customers pc.

Last week, I installed a new release. As soon as the main form came up, it
gave an out of memory message. I have now spent a week on this, and beleive
the out of memory message is a red herring.

After installing and getting this problem, I discovered that VS(visual
studio) 6.0 sp5 had not installed on my development pc. I tried to reinstall
sp5 several times again, but it failed. Eventually, I uninstalled and
reinstalled VS6.0, and then applied sp5 without a problem.

However, I beleive that having installed software (build with no sp) at my
customer, it has 'downgraded' a dll or ocx on his machine (runs NT4, sp6).

I tried to reinstall the old software that was running at the customer
without a problem, and it now gives the out of memory message!

I am sure something in system32 has been overwritten, but have no idea what.

Any ideas please, before I spend another week on this!

Thanks

Garry
 
Looked in the wrong directory - your absolutely right - Should have looked
in the VB distributable one :-( didn't realised MS had done a sneaky update
on me :-)
 
Gary

You'd probably have more luck with all this in the VB ng

However, I think you are correct in the out of memory error statement - this
can happen if you install the package and a dll or ocx is missing or does
not get properly registered - that is what you should look at.

Check the target machine has all the ocx and dll files in the installation
package and that they are at least the same or greater versions than in the
installation package.

If the program still doesn't run on the target machine - try forcing
registration of the files (just drag them onto regserv32) and then try
running the program again. If that fixes it, then your installtion package
is not correctly registewring the files when it installs.
 
One other obvious point which I forgot to mention is - are you sure you have
collected all the (REDISTRIBUTABLE) files needed into the installation kit.
Be careful about what you redistribute (things like wininet.dll should never
be redistrubuted - even though the package and deployment wizard may list
it - you could really screw up the target machine otherwise)
 
Back
Top