Loading problem

[catocom]

I have two computers both are running the same vb5
program both setup the same as far as vb5 setup.
I downloaded a little treeview program, and it runs
fine on one computer, but on the other I keep getting
an error when loading the program.

It says it cannot load comctl32.ocx.

If I write a program with this control it loads fine.

Anyone have an idea what the problem is?

P.S. I ran that fix (from MS) on both computers.

[Sam Finch]

It Could be that the guys who wrote the program havn't run the fix so it's trying to load a differnt versoin of the controll which one computer has and one doesn't.

That's just a wild guess btw and I Can't thik of much to do about it unless you can get your hands on the original code. Try Contacting the people who wrote it, see if they've had any problems.

[mattbrown]

Check that the version of the control is the same on both computers.

You could copy the control from the computer that works to the computer that doesn't work, register it and then try to run the program again.

BEWARE: The above approach could break other applications, so unless you know what you are doing it is not advisable.


Regards

[catocom]

Thanks for the reply,

I thought that might be the case too Sam, but the file
is in the windows system dir.

The path in the error was pointing to the dir where
the program was at so I tried copying the .ocx
to that path, but that didn't work either.

?Stumped me?

[Edited by catocom on 07-11-2000 at 12:58 AM]

[catocom]

That was exactly it Matt!

Works like a charm now.

It seems if two controls are different,
but have the same name, it seems they would make
the newer one with a little different name
doesn't it ?

Oh well I learn something new everyday,
thats one reason I love programming.

Thanks Matt

[Edited by catocom on 07-11-2000 at 01:12 AM]

[mattbrown]

Great generally they do change the name a little if there are major changes to the code in a dll or ocx, however it is just a small bug fix etc. They probably just increase the build number. So the version goes from

2.1.4890
to
2.1.4891

which causes the problems.

Regards