I have a OCX control that I wrote that I use in any program that has to download stuff from the web.
Everytime I recompile the OCX I have to recompile all the applications that use it because it says this is not the one that was compiled with it.
Printable View
I have a OCX control that I wrote that I use in any program that has to download stuff from the web.
Everytime I recompile the OCX I have to recompile all the applications that use it because it says this is not the one that was compiled with it.
in the compile options tab (project...properties) there is a group of options that deal with compatibility, fiddle until satisfied!
In the compile tab you want to set the OCX to binary compatibility. When this is set, VB checks your OCX with a previous version of the OCX for compatbility. As long as you haven't removed any functionality you should be cool.
What I typically do is after I have a good version of my OCX (or dll) I make a copy and give it a name like MYOCX.CMP. I then enter this name in the compatible file area. There's a good article on MSDN entitled "When should I use version compatibility" that explains the most options. I found this very useful.
:):)