This is kind of an off the wall offer. We don't have ONEVENT or COMRETURNEVENT. However, there is a COMRETURNERROR. CRE allows com to return a message (in the event of a com side error) to the clientsON ERROR process. You MIGHT be able to it this way. The client is either idleing or working, but has instanciated the com. The client ON ERROR process would need to evaluate aerror. The sever would contain the timer. At the designated time, com would forward to an INTENTIONAL error, thus triggering CRE. CRE would trigger client's on error and return a pointer. The client on error process would determine if the error was really just a message from com to begin a task. Client would reset the error, maybe send com some new instructions or calibrations, and run the task. I have used on error to trigger certain kinds of maintenance. There is an example of CRE in the files section in the ADO Query Analyzer.

>'cos I don't know how to, so I'm not sure that is a better idea than using two timers.
>
>It just seemed appropriate to think of using VFP to do this natively. The batch is not separable into a standalone .exe, its part of the existing app. 'To a guy with a Swiss Army knife every task looks like vehicle maintenance.'
>
>I will try to find out how to address Task Scheduler from inside VFP.
>
>Cheers