On Fri, 21 Nov 2003 17:30:41 GMT, "Mike Thomas" <MikeAmca@Yahoo.com>
wrote:
[color=blue]
>I want to start this thread again - on my first attempt I was a little
>ambiguous and was not able to get the answer I need.
>
>I am trying to start Access 2000 on Windows NT 2000 Server by using the
>scheduler with the command line:
>
>"c:\Program Files\Microsoft Office\Office\msaccess.exe"
>"d:\Apps\ChangeManagement.mdb" /x StartLoad
>
>This works when I run it from the "run" box, or via the scheduler when I am
>logged on to the server. Access opens, the macro calls a procedure which
>does what it needs to do and then closes Access down.
>
>The scheduler, apparently, cannot start Access at 5:00 am when nobody is
>logged on. The scheduler's log will show "Access could not start" the next
>morning. The scheduler does successfully run a V FoxPro app before and a
>Cute FPT macro after trying to run Access, so I know the scheduler is OK.
>
>What I need to know is whether Access can be started on a server via the
>scheduler when nobody is logged on, and if so, how. I don't want to give up
>on the plan if it is doable.
>
>Many thanks,
>Mike Thomas
>[/color]
AFAIK the answer is No. See
http://support.microsoft.com/default...b;EN-US;257757
and
http://support.microsoft.com/default...66&Product=acc
The solution I would use in this situation is to write the code in
Visual Basic and to implement a true service with the aid of the "NT
Service Toolkit" from Desaware (
www.desaware.com).
HTH
Matthias Kläy
--
www.kcc.ch 
