Hi all,
I have searched hi and low, here and the I cannot find even a small hint as to the source of this problem
I have an application that creates references to a multiuse object contained within a thread-per-object ActiveX EXE. The multiuse class utilises a timer to provide a pseudo-async/multi-threaded execution model.
The application has installed and worked perfectly in over 100 instances, across just about every OS and service pack combination you can think of. However, I now have 2 sites where the application just will not run as expected
In both instances the application is installed on a Windows2000 Server.
What appears to be happening is that the timer control (used to generate a pseudo-thread) is only raising its event into the last object created. e.g.
Instance1 - working fine
add Instance 2 and Instance1 stops working ?!
I have found that I can workaround the problem by changing the multiuse interface on the ActiveX EXE to singleuse and recompiling. Thus a completely seperate process is spawned for each instance of the object that uses the timer.
Can anyone tell me why a change from multiuse to single use should effect the ability to receive events from a timer control ?
I don't want to rollout singleuse-thread-per-object everywhere as the machine resource requirements go through the roof !
I have searched hi and low, here and the I cannot find even a small hint as to the source of this problem
I have an application that creates references to a multiuse object contained within a thread-per-object ActiveX EXE. The multiuse class utilises a timer to provide a pseudo-async/multi-threaded execution model.
The application has installed and worked perfectly in over 100 instances, across just about every OS and service pack combination you can think of. However, I now have 2 sites where the application just will not run as expected
In both instances the application is installed on a Windows2000 Server.
What appears to be happening is that the timer control (used to generate a pseudo-thread) is only raising its event into the last object created. e.g.
Instance1 - working fine
add Instance 2 and Instance1 stops working ?!
I have found that I can workaround the problem by changing the multiuse interface on the ActiveX EXE to singleuse and recompiling. Thus a completely seperate process is spawned for each instance of the object that uses the timer.
Can anyone tell me why a change from multiuse to single use should effect the ability to receive events from a timer control ?
I don't want to rollout singleuse-thread-per-object everywhere as the machine resource requirements go through the roof !