Fred Hooper
fahooper at trapo.com
Sun Nov 2 11:00:44 CST 2003
I had a similar requirement but needed to be sure that the program kept running within the same original job. I solved it with another mdb. The other one has a table where I put information on what to do from the main program. So when I closed the main one and started the other one, the other one compacted and repaired the back end. As the back end will sometimes be on another server for me, I used (the free) PsExec from www.sysinternals.com to start a batch file there. Fred Hooper |-----Original Message----- |From: accessd-bounces at databaseadvisors.com |[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Tony Septav |Sent: Friday, October 31, 2003 6:14 PM |To: AccessD at databaseadvisors.com |Subject: [AccessD] ACC97 - Repair and Compact | | |Hey All |I have a program designed for a client that runs basically 24 |hours a day, 7 days a week collecting and processing data. Is |it possible to schedule a once weekly repair and compact |operation on both the frontend and backend (or even for now |just the backend). There is a lag/idle time between 1AM and |4AM, when no data is collected or processed. Any direction to |available code, ideas or programs would be appreciated. Thank you. | |_______________________________________________ |AccessD mailing list |AccessD at databaseadvisors.com |http://databaseadvisors.com/mailman/listinfo/ac|cessd |Website: |http://www.databaseadvisors.com |