When you re-compile a dll you can select an option to maintain binary compatiblity. When it is appropriate to do this, the result is that any code that uses the dll will not have to be recompiled to be able to do so.
There are a couple of steps that you must follow to be able to maintain binary compatibility:
- 1: Compile the dll and save it in a folder that you have created for the purpose of keeping your binary compatible dll. You need to keep this dll so that from now on any time you recompile your dll VB
will be able to use this dll as it creates the new dll.
- 2: On your project properties dialog select the Component tab and check the Binary Compatibility option in the Version Compatibility section. You will need to browse to the location of your compiled dll that you set aside for compatibility using the file browser dialog.
Now, when you rebuild your dll, binary compatibility will be maintained.
Behind the sceen VB
uses the GUIDs and type library in your previously compiled dll to determine the GUIDs that are required to maintain compatibility, and it also checks on the differences between the existing dll and the new one being compiled to determine if binary compatibility can be maintained.
In your case, if you can get a copy of the origianlly compiled dll, you should be able to drop that into a folder and use it for the referenced binary compatibility resource.
There are numerous books and resoures that can step you through all of this. One very good book on ActiveX in Vb
is Dan Appleman's Developing Activex Components With Visual Basic 6.0. You can probably pick up a used copy on the internet for just a few bucks.
How to use a forum to help solve problems