Hi Reg,
I think that this could be done from any one of the workstations that has
Access installed, if I understand this correctly.
(I'm thinking that it doesn't matter HOW the data gets updated, as long as
it DOES get updated.)
1.) Use the Window Task Scheduler (on the workstation) to start up a totally
seperate, new, Access .MDB file.
2.) This MDB is specifically designed, and it's sole purpose is, to update
the tables in the backend database(s)
3.) It contains an Autoexec macro / code that updates the tables that are
stored in the backend, using the UNC file path to the backend with the
Linked Table Manager. This MDB should do it's thing, and then use
Application.Qui t to close itself when finished.
4.) I'd also consider using a DOS batch file that first uses Jetcomp (the
latest version accepts command-line parameters) to back up and compact these
files, then opens the MDB file above to do the updates.
5.) Use a .PIF file to run the .BAT file, which will allow you to use a
"Close on Exit" on the DOS window, making the whole sequence transparent to
the person who de-activates the screensaver in the morning. (Avoids the
"What the heck is this?" factor. )
All of the above is theoretical, and is also something that I am considering
for my own use.
Comments, anyone?
Don
"Reg" <re**********@g ov.ab.ca> wrote in message
news:9e******** *************** ***@posting.goo gle.com...
At present I'm running a number of macros with a schedular on my
computer to update and maintain databases within our network. All my
backends contain the tables that the macros update. But all the
backends are on servers that do not have access loaded on them. I
don't think it's possible to activate these macros from the servers
schedular without access being present. Is this true?
Thanks
Reg