moving a project with activeX to another computer

[petibub]

Hi!

I've got a very nasty problem. I have several VB projects which contain activeX objects I developed. Everything worked fine until I started to share the sources between several computers. Starting a VB project on another machine I get a message, that my ActiveX classes couldn't be loaded. Thus, I compiled the ActiveX on that computer and I could create a new project using this ActiveX. But, loading my old projects I still get the same error message and the ActiveX is displayed as a picture box :-(

Of course, I could delete the ActiveX object in my VB project, and create it again. But, the project files would change - moving to another computer I'd start with the same problem again.

Do you know a way to solve my problem and avoid changing the .vbp files?

[Hack]

What kind of files are the activex objects? What are they?

[petibub]

I use two ActiveX controls, wich are compiled to .ocx files. Particularly, I use a group project to code the ActiveX control and a test program for this control. Once the activeX control was compiled as .ocx I added it to a .exe project. Then, I moved the .exe project to another machine and the problems began.

br, petibub

[Hack]

Are you sure these OCX files are getting properly registered when they get installed?

Have you tried manually registering them with RegSvr32?

[petibub]

Yes, they are properly registered.

I found the problem: changing the computer I changed the OS. On the original machine I had Win2000 installed in C:\Winnt. On the new computer I have WinXP installed in C:\Windows. The compatibility mode of the ActiveX control was set to binary compatibiliy to file in C:\winnt\system32\myocx.ocx, according to the standard location of activeX controls on the Win2000 computer. Moving to the XP-machine, the compatibility file couldn't be found and a new control was compiled with the same name but not compatible! Thanks MS for missing around with folder names :-(

After unregistration of the failed control, adaptation of the path for the compatibility, and compiling the new (working) control, my old projects are able to load my controls!

Thanks for the assistence,

petibub