I would like to scan these machines in the same way as you have but I am
unable to download COM Explorer 2.0 from www.4dev.com
Do you know where else I can get a hold of a copy of this?

Thanks
Jo

-----Original Message-----
From: Peter-John Lightfoot [mailto:peter-johnl@a...]
Sent: 23 January 2003 10:32
To: professional vb
Subject: [pro_vb] RE: Run-time error 372 Failed to load control
mscomctl.ocx.


I did this only this morning to sort out an ocx problem: (one machine
worked
fine, the other not, while the versions of their installed ocx's seemed
to
be the same)...

With COM Explorer 2.0 (very neat tool!) I compared the development
machine
with both of these at once. The resulting columns are: Class, Version,
Machine1 and Machine2, where Class and Version list all the classes
registered on the developer's machine, and Machine1 and Machine2 would
be
given as Registered (i.e. everything's fine), Version x.xx (if a
different
version is installed on the target) or Missing!

I then just had to see which components are registered on Machine1 and
missing on Machine2, and I ended up with the following list:
ComCt232.ocx
MSDatRep.ocx
MSMask32.ocx
RichTx32.ocx
MSBind.dll
MSXml2.dll
SQLXMLX.dll

I now only need to ensure that some of these components (I'll test which
ones they are) are installed properly with deployment of my App.

Ciao,
Pj

-----Original Message-----
From: Jo Spiller [mailto:Jo.Spiller@E...]
Sent: 22 January 2003 15:49
To: professional vb
Subject: [pro_vb] RE: Run-time error 372 Failed to load control
mscomctl.ocx.


Thanks for all your suggestions. It's good to see a glimmer of hope on
this one. I'll let you know how we get on.

Cheers

Jo

P.S. That's Jo as in the opposite end of the country, I'm afraid!!

-----Original Message-----
From: Mark Roworth [mailto:mark.roworth@b...]
Sent: 22 January 2003 11:58
To: professional vb
Subject: [pro_vb] RE: Run-time error 372 Failed to load control
mscomctl.ocx.



Jo

I do not fully understand the complications of DLLs, but have spent some
time working on install programs. It sounds as if some of the DLLs have
been
updated, but not all of them and hence some are out of sync with others.
The
most common culprits for this is oleaut32, comcat32 and a few others.
One
way that sometimes fixes the problem is to install the latest Windows
service pack. However, the ocxs you are quoting are VB ocxs, I believe.
So,
if a windows service pack doesn't work, what you could do is install VB
and
it's latest service pack on the offending machines to update the dlls,
ocxs
and then uninstall them (so as not to use up licences) which should
leave a
nice updated set of system files behind.

Other than that, dunno!

Mark Roworth
Dolphin Computing Ltd
01273 262865
mark.roworth@b...


PS. That's not Jo Spiller as in Jo and Dave in Brighton, is it?


-----Original Message-----
From: jo.spiller@e... [mailto:jo.spiller@e...]
Sent: 22 January 2003 11:55
To: professional vb
Subject: [pro_vb] Run-time error 372 Failed to load control
mscomctl.ocx.


We have rolled out a version of our VB application and it works OK on
most
machines.  The problem we have is that on particular machines we get the
following error message:

'Run-time error 372 Failed to load control mscomctl.ocx. Your version of
mscomctl.ocx may be outdated. Make sure you are using the version of the
control that was provided with your application'

The error occurs when the MDI frame is first being instantiated. On
these
machines another particular application has been installed and we reckon
that it is overwriting some of the run time files.

We have checked to find other versions of this file and found an older
version and temporarily removed them and replaced them with our rolled
out
version (which we know works) and re-registered.  Now we have a machine
that only has 1 version of mscomctl.ocx (our working version) and re-run
our application and it still raises the same error '372'.
We did find documentation to use com redirection which was to create a
0kb
file the same name as our exe but to suffix .local.  What this does is
to
not look in the registry or system32 but to use run time objects in the
application directory.  The same error was still raised.
We expected a lock on the applications directory mscomctl.ocx but the
lock
was still in system32 mscomctl.ocx.
Although the error states a problem with mccomctl.ocx we think that is
might be on a dependant file that mscomctl.ocx is using.

If anyone can shed any light on this, how we can get this application
running on these machines without reinstalling the whole PC, we will be
very grateful.

Jo







______________________________________________
"The information contained in this communication is confidential and
may be legally privileged.  It is intended solely for the use of the
individual or entity to whom it is addressed and others authorised to
receive it.  If you are not the intended recipient you are hereby
notified that any disclosure, copying, distribution or taking action
in reliance of the contents of this information is strictly prohibited
and may be unlawful.  Absa is liable neither for the proper, complete
transmission of the information contained in this communication, nor
for any delay in its receipt, nor for the assurance that it is
virus-free."