Hi Dave,

did you put the .dll and .ocx under sourcesafe as well? Because when
you build the project you should have the binary reference of the
activex object.
After you build the project, unregister the ocx from your computer,
get the latest from source safe (or the one built), register it
and open the IDE again. It seems that there is no compatibility
between the 'official' build ocx and the one in your computer.
As far as I know, there are no issues regarding ocx. We have tens
of them in our apps and they all work fine. But we have problems
like yours (known as dll's hell) when someone with a wrong
version in his/her computer opens the project in the IDE.
Most of the time these problems go away 1) unregister all
components in the personal computer 2) delete the component
3) run RegCLean.exe. After you have done that, load main application
in the IDE (without the activex) and run with a full compile:
you should get a 'object not register' error. Copy the 'official'
component, register it and load the app again. Do this for all
activex and you should be fine.


Marco

> Hello all
    We have a project here that has multiple dlls and user controls in 
it.  We found that when we build the project that all works fine, and 
compatibilities are set to binary.  Then when the project is checked into 
source safe, and checked back out, running the exe works fine, however if 
we open the code of the exe and try to run it for debugging we get a bad 
compatibility, we have narrowed it down to the 2 custom user controls that 
are referenced.  We can change the compatibility of the user controls to 
project and recompile them all works, giving the warning that the control 
has been updated.  Is there an issue with using binary compatibility on 
user controls?  We would really like to avoid having to rebuild these 
controls every time we need to debug the project.  Thanks for any help.
 
Dave