>Hi,
>
>I'm building an application and another co-worker wants to add a timer to the _screen to manage the size of another screen that is going to act like a startup screen and be up all the time. Does anyone know of problems with timers running under the _screen, just don't feel good about a timer running all the time, also it consumes processing power. Any issues with this?
>
>Thanks.

Roy,

I have found timers firing in the middle of a rather time consuming grid refresh (vfp6sp5). In that case, the this within the timer may refer to the grid.

The only solution I have found is to skip a cycle if that is the case

** Timer Class is called QueueProcess

&& Timer event

local obj
obj = this
if( Proper(obj.Class) == Proper('QueueProcess') )  && good object
	if( empty(_triggerlevel) )  && not within a trigger
		obj.Enabled  = FALSE	&& stop timer event

                && process

		obj.Enabled = TRUE	&& restore timer event
	endif
else
     && skip a cycle

*!*  acti screen
*!*  ? time(), ' Class: ', obj.Class, ' ParentClass: ',obj.Parent.Class, chr(7)
endif