<div>
Compatibility is set to None.<br />
<br />
You must set Binary Compatibility for your OCX. Otherwise you get a new GUID every time it is compiled.<br />
There is no need to do this on Win2K, you can build the application and OCX on WinNT. Also no need to overwrite OlePro32.Dll.<br />
<br />
Once you build the OCX with Binary compatibility on, recompile your Exe. Finally install OCX and Exe on Win2K using a deployment wizard. You can also do it manually but you will have to register the OCX with RegSvr32.exe.<br />

</div>


<div>
Yes, I think you are correct. &nbsp;I am wondering if I can achieve the same results by recompiling the OCX on the new Win2k machine (either with binary compatibility or none). &nbsp;My objective is to make the Win2k machine the primary build machine for both the OCX and EXE. &nbsp;If I can't find a solution for the Win2k machine, my backup plan B is to just copy my EXE project code changes back to the WInNT machine and compile my EXE there. &nbsp;Since I currently have no code changes in the OCX, &nbsp;I'd rather not risk messing up the original WinNT configuration.<br />
<br />
Do you think re-compiling the OCX on the Win2k machine will work? &nbsp;If so, should I make it binary compatible?<br />
<br />
Thanks again.
</div>


<div>
Recompiling the OCX did the trick. Mamy thanks.
</div>


<div>
<div class="content wysiwyg-content">
I have a VB6 project/application that includes a reference to my OCX which has been working for years on NT. &nbsp;Recently we moved the project and all 3rd party components to Win2k. &nbsp;Everything works except for the case where I am setting at runtime the value of a radio button (used as a constituent control) through a function in my ocx. &nbsp;In this case I receive Automation error 439, followed by Automation error 440. &nbsp;<br />
<br />
In troubleshooting I have:<br />
1. Reloaded VB up to SP6<br />
2. Compared and swapped out olepro32.dll with the NT version (5.0.4512)<br />
3. Re-registered my OCX<br />
<br />
I also have other copies of my OCX in the registry caused by previously installing the built application (EXE) on the Win2k machine. &nbsp;The OCX has not been built on the new WIn2k machine, but on the original WinNT machine. &nbsp;Compatibility is set to None.<br />
<br />
Should I try recompiling the OCX on the new Win2k machine? &nbsp;Has anyone ever experienced something like this working on NT but not on Win2k due to OS file/version differences alone?<br />
<br />
Thank you.
</div>
</div>


I have a VB6 project/application that includes a reference to my OCX which has been working for years on NT.  Recently we moved the project and all 3rd party components to Win2k.  Everything works except for the case where I am setting at runtime the value of a radio button (used as a constituent control) through a function in my ocx.  In this case I receive Automation error 439, followed by Automation error 440.  

In troubleshooting I have:
1. Reloaded VB up to SP6
2. Compared and swapped out olepro32.dll with the NT version (5.0.4512)
3. Re-registered my OCX

I also have other copies of my OCX in the registry caused by previously installing the built application (EXE) on the Win2k machine.  The OCX has not been built on the new WIn2k machine, but on the original WinNT machine.  Compatibility is set to None.

Should I try recompiling the OCX on the new Win2k machine?  Has anyone ever experienced something like this working on NT but not on Win2k due to OS file/version differences alone?

Thank you.

Error 439 on Win2000, but works on NT

Visual Basic is Microsoft’s event-driven programming language and integrated development environment (IDE) for its Component Object Model (COM) programming model. It is relatively easy to learn and use because of its graphical development features and BASIC heritage. It has been replaced with VB.NET, and is very similar to VBA (Visual Basic for Applications), the programming language for the Microsoft Office product line.

Visual Basic Classic

Programming includes both the specifics of the language you’re using, like Visual Basic, .NET, Java and others, but also the best practices in user experience and interfaces and the management of projects, version control and development. Other programming topics are related to web and cloud development and system and hardware programming.