Hi,
I have written a simple exe that uses an ActiveX dll that I have also written.
For historical reasons the ActiveX dll uses (declares) a type as well as its class interfaces.
If I run the exe with the original dll all is fine. If I make a change to the code in the dll and recompile the exe no longer runs. It will do something (an hour glass flashes) but then it exits cleanly.
If I compile the dll with binary compatibility all is ok.
I have tried to debug the exe using Visual Studio. A few dlls are loaded but then the program exits (cleanly with a return code of 0) before the form_load sub.
In the globals of the exe I have declared :
In the form_load sub I instantiate the object.
My guess is that the program is failing on one of the global statements. I am uncertain how I can confirm this.
How do I trap the error in the exe on the odd case I use a dll that has not been compiled with binary compatibility?
Any advice would be appreciated.
Daniel.
I have written a simple exe that uses an ActiveX dll that I have also written.
For historical reasons the ActiveX dll uses (declares) a type as well as its class interfaces.
If I run the exe with the original dll all is fine. If I make a change to the code in the dll and recompile the exe no longer runs. It will do something (an hour glass flashes) but then it exits cleanly.
If I compile the dll with binary compatibility all is ok.
I have tried to debug the exe using Visual Studio. A few dlls are loaded but then the program exits (cleanly with a return code of 0) before the form_load sub.
In the globals of the exe I have declared :
Code:
Public value1 As New ClassDefinition
Dim value2 As vbreference.embeddedtype
Code:
Set value1 = New ClassDefinition
How do I trap the error in the exe on the odd case I use a dll that has not been compiled with binary compatibility?
Any advice would be appreciated.
Daniel.