I created a auto run macro in Excel using VBA. An access database kicks off
via windows scheduler and creates data files needed by excel. Once the files
have been created, before access closes, it opens the excel spreadsheet where
the auto run macro is stored. This process is set for early in the morning,
but it seems to stall or "pause" after excel starts. Once I unlock the
machine, the macro "unpauses". Is this an excel issue? Is their code to
prevent this from happening?

Does your machine require you to sign on with a password? I built an auto
scheduler and found that newer (2003+) versions of windows require that a
password be set on the machine, or the machine has to be unlocked to run a
scheduled task. Someone else might have more info on the subject.
--
-John
Please rate when your question is answered to help us and others know what
is helpful.


"Vinny P" wrote:

I created a auto run macro in Excel using VBA. An access database kicks off
via windows scheduler and creates data files needed by excel. Once the files
have been created, before access closes, it opens the excel spreadsheet where
the auto run macro is stored. This process is set for early in the morning,
but it seems to stall or "pause" after excel starts. Once I unlock the
machine, the macro "unpauses". Is this an excel issue? Is their code to
prevent this from happening?

Yes, however, windows scheduler works fine. My User name and pw is stored.
The scheduler kicks of the access macro first and access calls excel. Its
when the excel macro begins, the code appears to be stuck ONLY when the pc is
in a locked state.

"John Bundy" wrote:

Does your machine require you to sign on with a password? I built an auto
scheduler and found that newer (2003+) versions of windows require that a
password be set on the machine, or the machine has to be unlocked to run a
scheduled task. Someone else might have more info on the subject.
--
-John
Please rate when your question is answered to help us and others know what
is helpful.


"Vinny P" wrote:

I created a auto run macro in Excel using VBA. An access database kicks off
via windows scheduler and creates data files needed by excel. Once the files
have been created, before access closes, it opens the excel spreadsheet where
the auto run macro is stored. This process is set for early in the morning,
but it seems to stall or "pause" after excel starts. Once I unlock the
machine, the macro "unpauses". Is this an excel issue? Is their code to
prevent this from happening?

Could excel be waiting for a user to allow macros to run?

Could your code be waiting for a user to dismiss a msgbox?

Vinny P wrote:

Yes, however, windows scheduler works fine. My User name and pw is stored.
The scheduler kicks of the access macro first and access calls excel. Its
when the excel macro begins, the code appears to be stuck ONLY when the pc is
in a locked state.

"John Bundy" wrote:

Does your machine require you to sign on with a password? I built an auto
scheduler and found that newer (2003+) versions of windows require that a
password be set on the machine, or the machine has to be unlocked to run a
scheduled task. Someone else might have more info on the subject.
--
-John
Please rate when your question is answered to help us and others know what
is helpful.


"Vinny P" wrote:

I created a auto run macro in Excel using VBA. An access database kicks off
via windows scheduler and creates data files needed by excel. Once the files
have been created, before access closes, it opens the excel spreadsheet where
the auto run macro is stored. This process is set for early in the morning,
but it seems to stall or "pause" after excel starts. Once I unlock the
machine, the macro "unpauses". Is this an excel issue? Is their code to
prevent this from happening?

--

Dave Peterson

Thats what it seems like, but the macro does not require user input. No
message boxes. Perhaps it is something in my code preventing excel from
running while locked?

"Dave Peterson" wrote:

Could excel be waiting for a user to allow macros to run?

Could your code be waiting for a user to dismiss a msgbox?

Vinny P wrote:

Yes, however, windows scheduler works fine. My User name and pw is stored.
The scheduler kicks of the access macro first and access calls excel. Its
when the excel macro begins, the code appears to be stuck ONLY when the pc is
in a locked state.

"John Bundy" wrote:

Does your machine require you to sign on with a password? I built an auto
scheduler and found that newer (2003+) versions of windows require that a
password be set on the machine, or the machine has to be unlocked to run a
scheduled task. Someone else might have more info on the subject.
--
-John
Please rate when your question is answered to help us and others know what
is helpful.


"Vinny P" wrote:

I created a auto run macro in Excel using VBA. An access database kicks off
via windows scheduler and creates data files needed by excel. Once the files
have been created, before access closes, it opens the excel spreadsheet where
the auto run macro is stored. This process is set for early in the morning,
but it seems to stall or "pause" after excel starts. Once I unlock the
machine, the macro "unpauses". Is this an excel issue? Is their code to
prevent this from happening?

--

Dave Peterson

If it is waiting for someone to approve macro's as Dave suggested, you can
get a certificate such as selfcert (the one i use, free) and you can
digitally sign your work, once accepted, the accept macro box no longer shows
up.
--
-John
Please rate when your question is answered to help us and others know what
is helpful.


"Vinny P" wrote:

Thats what it seems like, but the macro does not require user input. No
message boxes. Perhaps it is something in my code preventing excel from
running while locked?

"Dave Peterson" wrote:

Could excel be waiting for a user to allow macros to run?

Could your code be waiting for a user to dismiss a msgbox?

Vinny P wrote:

Yes, however, windows scheduler works fine. My User name and pw is stored.
The scheduler kicks of the access macro first and access calls excel. Its
when the excel macro begins, the code appears to be stuck ONLY when the pc is
in a locked state.

"John Bundy" wrote:

Does your machine require you to sign on with a password? I built an auto
scheduler and found that newer (2003+) versions of windows require that a
password be set on the machine, or the machine has to be unlocked to run a
scheduled task. Someone else might have more info on the subject.
--
-John
Please rate when your question is answered to help us and others know what
is helpful.


"Vinny P" wrote:

I created a auto run macro in Excel using VBA. An access database kicks off
via windows scheduler and creates data files needed by excel. Once the files
have been created, before access closes, it opens the excel spreadsheet where
the auto run macro is stored. This process is set for early in the morning,
but it seems to stall or "pause" after excel starts. Once I unlock the
machine, the macro "unpauses". Is this an excel issue? Is their code to
prevent this from happening?

--

Dave Peterson

Or change the security level to the lowest choice to allow every macro to run.
MS doesn't recommend this.

Vinny P wrote:

Thats what it seems like, but the macro does not require user input. No
message boxes. Perhaps it is something in my code preventing excel from
running while locked?

"Dave Peterson" wrote:

Could excel be waiting for a user to allow macros to run?

Could your code be waiting for a user to dismiss a msgbox?

Vinny P wrote:

Yes, however, windows scheduler works fine. My User name and pw is stored.
The scheduler kicks of the access macro first and access calls excel. Its
when the excel macro begins, the code appears to be stuck ONLY when the pc is
in a locked state.

"John Bundy" wrote:

Does your machine require you to sign on with a password? I built an auto
scheduler and found that newer (2003+) versions of windows require that a
password be set on the machine, or the machine has to be unlocked to run a
scheduled task. Someone else might have more info on the subject.
--
-John
Please rate when your question is answered to help us and others know what
is helpful.


"Vinny P" wrote:

I created a auto run macro in Excel using VBA. An access database kicks off
via windows scheduler and creates data files needed by excel. Once the files
have been created, before access closes, it opens the excel spreadsheet where
the auto run macro is stored. This process is set for early in the morning,
but it seems to stall or "pause" after excel starts. Once I unlock the
machine, the macro "unpauses". Is this an excel issue? Is their code to
prevent this from happening?

--

Dave Peterson


--

Dave Peterson