scheduled tasks and access reports

[evilmousse]

I've got an MSaccess adp that, upon clicking it or
typing it's name in command shell, will open,
print some reports to pdf, and quit.
This much works on both my development computer
and the server it will run on.
When I create a scheduled task on my computer,
it also works. However when i try to do the same
on the server, it fails.
As near as I can tell, the server runs its
scheduled tasks in a service context, whereas
my computer runs them in an application context.
And access apparently isn't happy with being
a service, it will load into memory and stay there
taking no CPU time.
So if anyone knows where windows's setting to
have scheduled tasks open in application rather
than service mode, let me know please.

-g

 

[bcastner]

I think you are seeing a permissions issue, rather than a Service v. Application one.

Scheduled Tasks is a service; whatever it calls to execute need not be a service nor is made one automaticly by being scheduled on the server.

 

[evilmousse]

Ok, that's good to hear, but my problem remains.

The same executable, and the same settings for
scheduled tasks to run them will run differently
on my server vs my development computer.

I believe it to be incorrectly running as a service
on the server because MSACCESS.EXE makes an appearance
on task manager's processes tab, but not on it's
application tab.
On my development machine, MSACCESS.EXE makes an
appearance on both tabs, as it should.

So, settings for the executable and the scheduled
task being the same in both cases, I'm guessing
there's an OS setting somewhere that I'm not finding.

The permissions, near as I can tell, are correct.
I gave it permissions to run as the user I logged
in as and successfully executed the file by hand.

-g