Sayan Mukherjee
March 13th, 2001, 09:24 PM
Hi Codegurus,
I am facing a weird problem with the timer
control of VB.
I have a VB form which has the timer in it. The
timer is set to 5 seconds interval. When this
5 sec expires, the Timer() method is called by
the VB framework automatically.
The Timer() method has a COM server method call
in it. So every 5 seconds the server method call
should take place.
If I run the application in the debug mode (by
pressing F5 button from the VB Design menu),
there is no problem; but if I compile the EXE
and run it from the desktop, the timer function
fires only once. The entire Form freezes after
this and there is no response on the Form.
Just for information:
- The COM object is instantiated using
CreateObject()
- I am running this application on
Windows 2000
- The server side code is written in VC 6.0.
I have used the ATL COM wizard for building
the class and the interface (i.e. the skeleton
code)
What could be the reason for this? If this is a
VB bug, please suggest a workaround. This is
really URGENT!!!!!
Thanks in advance,
With best regards,
Sayan
Sayan Mukherjee
Calcutta (INDIA)
Email: sayan1968@yahoo.com
I am facing a weird problem with the timer
control of VB.
I have a VB form which has the timer in it. The
timer is set to 5 seconds interval. When this
5 sec expires, the Timer() method is called by
the VB framework automatically.
The Timer() method has a COM server method call
in it. So every 5 seconds the server method call
should take place.
If I run the application in the debug mode (by
pressing F5 button from the VB Design menu),
there is no problem; but if I compile the EXE
and run it from the desktop, the timer function
fires only once. The entire Form freezes after
this and there is no response on the Form.
Just for information:
- The COM object is instantiated using
CreateObject()
- I am running this application on
Windows 2000
- The server side code is written in VC 6.0.
I have used the ATL COM wizard for building
the class and the interface (i.e. the skeleton
code)
What could be the reason for this? If this is a
VB bug, please suggest a workaround. This is
really URGENT!!!!!
Thanks in advance,
With best regards,
Sayan
Sayan Mukherjee
Calcutta (INDIA)
Email: sayan1968@yahoo.com