Hi Steven,
I developed a utility application several years ago to do part of what
you seek and more to boot.
What it does for you: Enter as many MDB full pathnames as you like.
With each source MDB you also enter the start of a Backup tree for
that application. In that tree is a folder for each day of the week.
Typically that Backup tree begins at ThisDrive:\ThisFolder\BAckups\...
It could as easily be TheCDDrive\...\...
When you backup today you over write last week's backup - you have a
week to copy it out if you choose. I dedicate a copy of the utility
to each application. It's a real life saver during development I get
an automatic backup each time I exit the app. In your case, one copy
would do the whole job.
As each MDB is addressed it is first renamed (by changing its
extension) in place. It is then compressed into its backup location
for the day of the week. The compressed file is copied back into the
original folder with the original name.
Files are addressed in entry order. Every major step of the operation
on each file is appended to the log just before execution. Any errors
are also logged. The log file is created in the folder where the
utility application resides.
--------- Assuming the scheduler fires it off, the above would leave
you with your files backed up and compacted and ready for the next
operation. ----------------
You didn't indicate what supervision you want to have over the
execution of the individual applications. Would just delaying a set
time between the execution of the applications do it?
HTH
