I have seen problems with random errors saying a property does not exist for an object. I have traced this to when the timer is running in one data session, and the user has gone to a second data session when the timer fires. I have not seen this when the event calls a method on itself before attempting to access any other objects. It appears it forces itself back into the correct data session and all pieces of objects can be seen again. This also happens with the use of BindEvents.
Tracy -----Original Message----- From: MB Software Solutions General Account Sent: Monday, March 31, 2008 10:22 AM Tracy Pearson wrote: > My experience with timers, they can start firing, or queuing up a > massive succession. When I use them, I now disable them when entering, > and re-enable on exit. If there are other data sessions involved in > the application, make sure you call a user defined method of the timer > object from the event. Your code for the timer should be in the user defined method. > Hi Tracy, I agree with your disabling on entry/re-enabling on exit concept--I do that too, but I'd like to understand your logic of the using the UDF instead of putting the code in the Timer method. tia! --Michael _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/profox OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/[EMAIL PROTECTED] ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
