The answer to the first question is yes, you can write an application that will use a timer to update a table.

For the second question, the timer will live as long as the application that created it run and doesn't stop it. If you want the timer to fire as long as the server is running, run the application on the server and keep it running.

HTH

---

>I have a foxpro program (lets say progA) being used by 20 people accessing a table call person_tbl in Assign.dbc. What I want to do is create a seperate timer program (because my user will exit progA periodically) that will update the person_tbl. First, is it possible to create a seperate timer program (lets say a project ProgB) that can update the shared table in ProgA? Second, how can I keep the timer from terminating once I exit the ProgB program? What I mean is once the timer is started on the server, will it keep running even if I turn my machine off(the machine that executed the progB)?
>and Finally if the timer does continue, how do I turn it off, do I just restart the progB again and have a button turn the timer off?