Auto Schedule Access in Network Server

[Samantha]

Hi,

I would like to create a MsAccess program that automatically pulls data from
one SQL database, and writes it to another SQL database in scheduled
intervals, say 2 times a day. I need the Access program to be in the network
server because having it at anyone's computer might run the risk of someone
accidentally turning off the computer. Is it possible to use the scheduler at
a network server? Has anyone done this before?
Thank you in advance.

 

[Arvin Meyer [MVP]]

Servers (and NT based computers) use AT commands for scheduling. Try:

Start >>> Run >>> then type: cmd >>> then type: AT /?

you'll get a list of all the commands. There's also a GUI : WINAT in the
resource kit.

 

[Bill Edwards]

If you are using SQL Server, why not just create a SQL Server job and
schedule it inside SQL Server?

 

[David W. Fenton]

Servers (and NT based computers) use AT commands for scheduling.
Try:

Start >>> Run >>> then type: cmd >>> then type: AT /?

you'll get a list of all the commands. There's also a GUI : WINAT
in the resource kit.

From Win2K on, there's a wizard for doing it in the Accessories |
System Tools menu.

 

[Arvin Meyer [MVP]]

From Win2K on, there's a wizard for doing it in the Accessories |
System Tools menu.

The Task Scheduler, which is the applet you are talking about, will work
too. It is not the same as AT commands which can be used to control remote
computers as well. Old admin habits die hard. I've been using AT commands
since 1996.

 

[Arvin Meyer [MVP]]

If you are using SQL Server, why not just create a SQL Server job and
schedule it inside SQL Server?

Also a good choice, but more difficult than writing a query and running a
small bit of code from an AT command or the Task Scheduler. Also, AT
commands can be run from a remote machine with lesser priviledges than
running a SQL job. I guess it depends upon your preferences and role, which
you will use. An admin will use AT, a programmer will probably want the Task
Scheduler, and a SQL-Server database admin will most certainly choose the
SQL Job.

 

[David W. Fenton]

The Task Scheduler, which is the applet you are talking about,
will work too. It is not the same as AT commands which can be used
to control remote computers as well. Old admin habits die hard.
I've been using AT commands since 1996.

I've *never* used them! I used WinAT back in 1998 when I started
administering NT servers, because the AT command lines made my eyes
glaze over.

 

[Tony Toews [MVP]]

I would like to create a MsAccess program that automatically pulls data from
one SQL database, and writes it to another SQL database in scheduled
intervals, say 2 times a day. I need the Access program to be in the network
server because having it at anyone's computer might run the risk of someone
accidentally turning off the computer. Is it possible to use the scheduler at
a network server?

You may have a lot of trouble finding a server on which IT will allow
you to install an application, that is MS Access. I'd consider a SQL
solution if reasonable.

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm