I have had to train another VB programmer on my projects while I will be
gone for a few weeks.

We had a problem that once he couldn't open my projects, since he didn't
have the ocxs on his computer. We then checked out them and compiled.
It created two problems.
1) It couldn't provide the binary compatibility and changed it to 'No
compatibility', I think that it did not find the old class id in the
registry since the control was not registered before.
2) Once it compiles, it makes a new class id for the controls. Therefore the
project will not recognize the 'new' controls.
    In the frm, vbp files are written the old class id that is I assume
stored in the registry of my computer.

Try unregistering the ocx, then register the ocx from the source computer.
Change the Version Compatibility to binary and compile again. Binary makes
VB use the same class id and not to create a new one. The both of you will
be editing the same control with the same class id.

>

>
> Subject: Problem: VB using VSS with custom built ActiveX controls.
> From: "Bret Pelkey" <bret.pelkey@a...>
> Date: Tue, 13 Feb 2001 17:57:15 -0600
> X-Message-Number: 1
>
> Problem: VB using VSS with custom built ActiveX controls.
>
> Working with a team of 3 programmers using VB 6.0 SP4 with visual
SourceSafe
> 6.0. We have 2 projects both using the same custom ActiveX control we
> created. The problem we are having is that the ActiveX control project is
> not working with VSS. If one person opens and edits the ActiveX project
and
> recompiles. It no longer works with the other standard project on the
other
> work stations computers any more. The forms disappear and have to be re
> added to the project group. The only way we can get it work again is to
get
> the latest version of the ActiveX and recompile. But this destroys the
other
> two stations projects. (In other words a dog casing his tail) The other
> problem I'm having is that the ActiveX is only compatible with standard
> projects of last station that built the ActiveX.ocx file.
>
> Has any one else run in to this problem?
>
>
> ----------------------------------------------------------------------