Rocky Smolin - Beach Access Software
bchacc at san.rr.com
Thu Aug 10 14:51:50 CDT 2006
Thanks. I'll let the user's tech folks know. I'm sure they'll have questions. They're in Shanghai which makes it even more awkward. Rocky Jim Lawrence wrote: > Hi Rocky: > > Running the timer in the application can be complex, if the user is going in > and out, has to be a specific user etc. You can use command line scheduling. > On the older servers the "at" could be setup and on the new servers the > "schtasks" can be used. Example: > > schtasks /create /tn "MyExportApplication" /tr c:\apps\myexport.exe /sc > daily /sd 8/25/2006 /st 3:00 > > ...then it would run in the background with no processing time consumed. The > above application, named "MyExportApplication", would run the application > myexport (any executable, batch, script or even MSAccess app can be run), > runs daily, starting 25 August 2006, at 3:00am in the morning. The schedule > would be created by an admin person avoiding all the permissions issues. > > HTH > Jim > > -----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