[AccessD] Trigger code every day

The answer is "it depends."  We created a couple of products that run
like this.  The big gotcha is that it doesn't run as a service, and it
really isn't a good idea to install Access on a server.  Yes, it sucks
up cycles, not to mention the fact that when the server goes down, it
will come back up but your application won't.  The better way is not to
use Access for the app. 

When you say the app is going to "export some files",  what do you mean?
Are these files created by the app or by some other application, with
the desired program just checking for the existence of files and then
moving them somewhere?

Charlotte Foust

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Rocky Smolin
- Beach Access Software
Sent: Thursday, August 10, 2006 9:09 AM
To: Access Developers discussion and problem solving
Subject: [AccessD] Trigger code every day

Dear List:

A client needs to run a program every day at the same time to export
some files.  I'm thinking that I use the OnTimer event with some timer
interval (like 5 minutes) and check the clock to see if it's time to do
the export.  This app will run all the time in the background and reside
probably on their server.  Is this going to suck up a lot of server
cycles?  Is there a better way to do this?

MTIA

Rocky

-- 
Rocky Smolin
Beach Access Software
858-259-4334
www.e-z-mrp.com

-- 
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com