🚀 go-pugleaf

In article <6qpiaq$o4p1@piper.ncr.pwgsc.gc.ca>, "Chester Copeland" 
<Chester.Copeland***AT***pwgsc.gc.ca> says...
> I have done something similar. I ran an excel
> program once a day to publish charts to a web
> site. I used Winat.exe, which is just a GUI to the
> AT command. Have AT run Access, passing to it the
> name of the db to start. Create an aotorun macro
> in the Access database that does your job by
> calling other macros. Exit from the autorun macro.
> Make the AT command "Interactive" which will make
> it interact with anyone that is logged on the
> workstation. This is necessary so that when/if the
> prog issues a message box requiring a response,
> you will be able to respond. Otherwise the prog
> will hang. The AT command does not log on as a
> user. The prog is run as "system" or something
> similar.  Therefore, it will not have access to
> printers configured for any user. I had to mess
> with the registry to create a printer. I can't
> remember exactly how I did it.
> 
> Good luck
> Chester
> 
> 
> Jeriad Zoghby wrote in message
> <6qnn5r$obt$1@amdint2.amd.com>...
> >Does anyone know where I can find information and
> examples on NT at commands
> >(besides the NT help files)?  I would like to
> automate an Access macro to
> >run twice a day.  Has anybody done this?
> >Jeriad
> >
> >
> 
> 
> 
Yes, and while the access macro is running the user can break out of it, 
and give himself domain admin rights because he is logged in as system.

Presumably you have other stuff running of AT, and want to leave it as 
SYSTEM.  You should therefore SU to another account with less access if 
you are going to have the program run interactively.