Access can't run when I'm logged off?

[bernard.thouin]

Hi,

I have an Access 2003 app (accessing an Access 2002-2003 DB) that runs
every day at a given time on an XP Pro PC. I've used XP's built-in
scheduler to set up the app to run every day at a fixed time (17:30).
The scheduler asks for user and password to run the app under. The app
has no forms at all, it just runs a macro that calls a function that
does all the work, which is purely DB-related (reading from one remote
DB, processing the data, writing the processed data into another remote
DB). So it has actually "no UI".

On Friday I had to leave the office early, so I just logged off (but I
let my PC running), thinking that the scheduler should be able to run
the app later on. However, this morning when logging in, I only found a
fatal error message ("Access has found a problem and needs to close, do
you want to report the problem to MS..."), and I can see that the app
has not run at all.

Does that mean that "unattended" operations are not at all possible
with Access ? What's the problem ?

Tanks for help.

Bernard

[David W. Fenton]

be************@ubs.com wrote in
news:11**********************@i42g2000cwa.googlegr oups.com:

Does that mean that "unattended" operations are not at all
possible with Access ? What's the problem ?

Access is not a system service. It has a user interface, and has to
be logged on to be able to run.

Lock your workstation instead and that will allow it to run.

--
David W. Fenton http://www.dfenton.com/
usenet at dfenton dot com http://www.dfenton.com/DFA/

[Tom van Stiphout]

On Mon, 09 Oct 2006 15:04:38 -0500, "David W. Fenton"
<XX*******@dfenton.com.invalidwrote:

I've never tried this, but I would be curious what would happen if I
had a Service which created an Access.Application object and made it
do things...

-Tom.

>be************@ubs.com wrote in
news:11**********************@i42g2000cwa.googleg roups.com:

>Does that mean that "unattended" operations are not at all
possible with Access ? What's the problem ?

Access is not a system service. It has a user interface, and has to
be logged on to be able to run.

Lock your workstation instead and that will allow it to run.

[David W. Fenton]

Tom van Stiphout <no*************@cox.netwrote in
news:f9********************************@4ax.com:

On Mon, 09 Oct 2006 15:04:38 -0500, "David W. Fenton"
<XX*******@dfenton.com.invalidwrote:

>>be************@ubs.com wrote in
news:11**********************@i42g2000cwa.google groups.com:

>>Does that mean that "unattended" operations are not at all
possible with Access ? What's the problem ?

Access is not a system service. It has a user interface, and has
to be logged on to be able to run.

Lock your workstation instead and that will allow it to run.

I've never tried this, but I would be curious what would happen if
I had a Service which created an Access.Application object and
made it do things...

Services are not supposed to have a UI.

You could try launching it with SrvAny, which is available in all
the Windows Server toolkits.

But I'd only use it in production with apps that were designed with
running as a service in mind.

--
David W. Fenton http://www.dfenton.com/
usenet at dfenton dot com http://www.dfenton.com/DFA/