Scheduling Software needed

[ipr1]

I am looking for some scheduling software to meet the following requirements:

The ideal requirements for a new scheduling tool would be:
• More robust than LaunchPad, but less complicated that Maestro
• ability to initiate specific Access macros (not using an autoexec macro) REQUIRED
• must provide detailed audit logs to show success or failure of each job REQUIRED
• ability to monitor shares for files or file changes
• Networked version for shared access?
• Must be controlled from within the team

Does anybody have any suggestions?

Thank you.

 

[KeithG]

You probably won't get many replies because your question is to broad. You should ask more specific questions and I bet you will get better results because I don't even know were to start.

 

[The_Doc_Man]

Shoot, I've got an OpenVMS box that doesn't have a scheduler with THAT level of sophistication and history management...

You're asking for a lot, I think. Be prepared to compromise.

 

[ipr1]

You probably won't get many replies because your question is to broad. You should ask more specific questions and I bet you will get better results because I don't even know were to start.

Your point is well taken and thanks for voicing it.

We run a series of access programs throughout the day and want to automate the process by kicking each database off via a scheduler. Because of the nature of our work, we need to know what programs ran successfully and what programs failed.

I hope this explanation helps.

 

[The_Doc_Man]

Use Julius Caesar's approach - divide and conquer.

1. Use Windows Task Scheduler and the /X command-line option to trigger each Access run. The /X option triggers the macro named as the argument of the option. Obviously, the named macro must exist. It should also end with a Quit command (to exit from Access when it is done.)

2. As part of the run, have the macro run some code to update a file that is your log file of the runs. Presuming the application could know from within Access whether it worked or not, you hope to have a good log file for this.

3. There is an inherent problem in knowing whether a program failed from outside the program itself. One of the "Completeness" theorems (Goedel?) says that is true, and I have found it to be true as well. Only Access has any real hope of knowing whether an Access program worked. An outside program has to be at least as smart as Access to know if Access worked.