In NT use the "at" command:

AT [\\computername] [ [id] [/DELETE] ¦ /DELETE [/YES]]
AT [\\computername] time [/INTERACTIVE]
[ /EVERY:date[,...] ¦ /NEXT:date[,...]] "command"

"\\computername" Specifies a remote computer. Commands are scheduled on the local computer if this parameter is omitted.

"id" Is an identification number assigned to a scheduled command.
"/delete" Cancels a scheduled command. If id is omitted, all the scheduled commands on the computer are canceled.

"/yes" Used with cancel all jobs command when no further confirmation is desired.

"time" Specifies the time when command is to run.

"/interactive" Allows the job to interact with the desktop of the user who is logged on at the time the job runs.

"/every:date[,...]" Runs the command on each specified day(s) of the week or month. If date is omitted, the current day of the month is assumed.

"/next:date[,...]" Runs the specified command on the next occurrence of the day (for example, next Thursday). If date is omitted, the current day of the month is assumed.

"command" Is the Windows NT command, or batch program to be run.

MIke...Is this for a batch file to be run on NT? WHat you are saying is write a batch file then execute it from the VB app?

Although the using a timer control is extra overhead you could use it to check the time and execute if the time is right. Or have your users use the system agent on win98 to execute a set time.

The AT command is a native NT command and will run either a batch file or a standard program.

I'm suggesting that you call the AT command from VB.

I wouldn't reccomend that you rely on your users because - despite their obvious and many charms - users are people too and have been known to forget things.

Mike
---
Mike_Lacey@Cargill.Com