I have an Access based system that includes Access programs run
automatically by the Windows scheduler. One runs every morning to
download xml data and load into Access. Another runs on Saturday and a
third on Sunday. I am looking for "best proactices" - a good solid way
to easily tell if any of these programs did not run or did not run to
completion.

Anyone have favorite ways of doing this?

bob

On Aug 15, 11:51*am, Bob Alston <bobalst... (AT) yahoo (DOT) com> wrote:
I've done this several ways. Either writing to a text log file (in
the programs directory), sending a email to someone, as well as
writing to the Windows Event Log. I'm not sure which is my
"favorite", but there is plenty of sample code out there (and in this
very newsgroup) to help start you on your way.

Even though I really don't have a favorite, the text log file has
always seemed to be the "cleanest" to me, but I agree with the reasons
for all the others. One application I did writes just about
everything it does to it's own Access "log table" which is then
exported to Excel. That one may be the "ugliest" to me, but it's what
the client wanted...

Bob Alston <bobalston9 (AT) yahoo (DOT) com> wrote in
news:mWU9o.8425$co1.6274 (AT) newsfe11 (DOT) iad:

I would generally want to avoid using an Access app for this
purpose, as the type of things you schedule on a windows server need
to have no UI. I would tend to implement such things with VBScript.

As to status, you'd build some form of logging, which means you'd
need error handling within your code so that an error wouldn't abort
your logging routine.

--
David W. Fenton http://www.dfenton.com/
contact via website only http://www.dfenton.com/DFA/

Just use SQL Server, SQL Server Agent.. and you can tell it to email
you when a process fails




On Aug 15, 9:51*am, Bob Alston <bobalst... (AT) yahoo (DOT) com> wrote: