Multiple instance of an activeX EXE
I created an activeX EXE composed of a class ClassA. This activeX is used by the applications appA and appB.
When I load the applications appA and appB they use the same instance of the activeX. And, when I stopp the application appB, it unloads the instance of the ActiveX. But like this instance is unique, the application appA (that is still loaded) is not able to work with the class of the ActiveX.
What I would like to know, it is how to load the ActiveX in the applications appA and appB so that they never use the same instance of the activeX EXE.
Either, how the ActiveX, when it is loaded could detect that there is already an other instance and how the ActiveX could create himself a second instance, independent of the first. And in this case, how unload the instance with which I work and not all instances.
any help welcome
thanks
When I load the applications appA and appB they use the same instance of the activeX. And, when I stopp the application appB, it unloads the instance of the ActiveX. But like this instance is unique, the application appA (that is still loaded) is not able to work with the class of the ActiveX.
What I would like to know, it is how to load the ActiveX in the applications appA and appB so that they never use the same instance of the activeX EXE.
Either, how the ActiveX, when it is loaded could detect that there is already an other instance and how the ActiveX could create himself a second instance, independent of the first. And in this case, how unload the instance with which I work and not all instances.
any help welcome
thanks
Who is Participating?
LVL 3
go in the project properties and set the threading to thread per object. each program will get a new instance of the active x exe
this will also take care of the unloading problem. each exe will only unload the instance of the active x exe they have and not all of them
Hi,
The reason it unloads it probably because you have your class set to multiuse. Set it to 3-singleuse, then each instance will use a separate class.
Zaphod.
The reason it unloads it probably because you have your class set to multiuse. Set it to 3-singleuse, then each instance will use a separate class.
Zaphod.
You can do this with a connector class:
--------------------------
VERSION 1.0 CLASS
BEGIN
MultiUse = -1 'True
Persistable = 0 'NotPersistable
DataBindingBehavior = 0 'vbNone
DataSourceBehavior = 0 'vbNone
MTSTransactionMode = 0 'NotAnMTSObject
END
Attribute VB_Name = "Connector"
Attribute VB_GlobalNameSpace = False
Attribute VB_Creatable = True
Attribute VB_PredeclaredId = False
Attribute VB_Exposed = True
Attribute VB_Ext_KEY = "SavedWithClassBuilder6" ,"Yes"
Attribute VB_Ext_KEY = "Member0" ,"RequestHandler"
Attribute VB_Ext_KEY = "Top_Level" ,"Yes"
Option Explicit
Public Property Get RequestHandler() As RequestHandler
Set RequestHandler = gRequestHandler
End Property
Private Sub Class_Initialize()
If gRequestHandler Is Nothing Then
Set gRequestHandler = New RequestHandler
End If
clientCounter = clientCounter + 1
End Sub
Private Sub Class_Terminate()
clientCounter = clientCounter - 1
If clientCounter = 0 Then
Set gRequestHandler = Nothing
End If
End Sub
This you must add to your ActiveX EXE in a global
code modul:
Public gRequestHandler As RequestHandler
The object gRequestHandler guaranties that only one
instance of your AxtiveX exe is running at the same time.
The client must create a connector object, to access
the your ActiveX class with:
Set ClientActiveXRef = ClientConnector.RequestHan
Therefore the ActiveX Exe is unloaded when the last
connector object is released ...
The idea for this is form microsoft ...
Best regards
WoK
--------------------------
VERSION 1.0 CLASS
BEGIN
MultiUse = -1 'True
Persistable = 0 'NotPersistable
DataBindingBehavior = 0 'vbNone
DataSourceBehavior = 0 'vbNone
MTSTransactionMode = 0 'NotAnMTSObject
END
Attribute VB_Name = "Connector"
Attribute VB_GlobalNameSpace = False
Attribute VB_Creatable = True
Attribute VB_PredeclaredId = False
Attribute VB_Exposed = True
Attribute VB_Ext_KEY = "SavedWithClassBuilder6" ,"Yes"
Attribute VB_Ext_KEY = "Member0" ,"RequestHandler"
Attribute VB_Ext_KEY = "Top_Level" ,"Yes"
Option Explicit
Public Property Get RequestHandler() As RequestHandler
Set RequestHandler = gRequestHandler
End Property
Private Sub Class_Initialize()
If gRequestHandler Is Nothing Then
Set gRequestHandler = New RequestHandler
End If
clientCounter = clientCounter + 1
End Sub
Private Sub Class_Terminate()
clientCounter = clientCounter - 1
If clientCounter = 0 Then
Set gRequestHandler = Nothing
End If
End Sub
This you must add to your ActiveX EXE in a global
code modul:
Public gRequestHandler As RequestHandler
The object gRequestHandler guaranties that only one
instance of your AxtiveX exe is running at the same time.
The client must create a connector object, to access
the your ActiveX class with:
Set ClientActiveXRef = ClientConnector.RequestHan
Therefore the ActiveX Exe is unloaded when the last
connector object is released ...
The idea for this is form microsoft ...
Best regards
WoK
Question has a verified solution.
Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.
Have a better answer? Share it in a comment.
All Courses
From novice to tech pro — start learning today.
