rusty.hammond at cpiqpc.com
rusty.hammond at cpiqpc.com
Thu Aug 10 11:24:55 CDT 2006
Rocky, Don't know how bad it's going to affect the server by running it directly on it with one process a day, but what we have done is setup another workstation that runs these type of things. Seems like once you automate one thing, then other items could suddenly be automated that noone had thought of before, then you could run into server issues with multiple processes running throughout the day. We're using MS Access with the OnTimer event and time checking just like you suggest. Pretty solid solution. HTH Rusty -----Original Message----- From: Rocky Smolin - Beach Access Software [mailto:bchacc at san.rr.com] Sent: Thursday, August 10, 2006 11: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 ********************************************************************** WARNING: All e-mail sent to and from this address will be received, scanned or otherwise recorded by the CPI Qualified Plan Consultants, Inc. corporate e-mail system and is subject to archival, monitoring or review by, and/or disclosure to, someone other than the recipient. **********************************************************************