Be aware that your database has to be open for Timer code to run. Having
Timer code constantly running will be a hit on the performance of everything
you do in the database. Consider splitting your database if you haven't
already done that. Since you want to periodically run some code, the only
thing that code could be doing is some addition or modification to one or
more tables. Consider creating an external database to contain the code you
want to run. In that database, create an autoexec macro to start the code
when the database file is opened. Use Windows Taskmaster to open that
database at specified times you set in Taskmaster. You can also have code
that closes the file after your code is finished running. Doing it this way
you avoid needing to have any database open when it's time to run the code
(the externeal database is automatically opened at the specified time) and
you avoid any performance hit on your primary database.
PC Datasheet
Providing Customers A Resource For Help With Access, Excel And Word
Applications
[email protected]