C
Chris
I have read a lot on this but haven't found my answer yet - hopefully someone
can point me in the right direction.
I have created an application that has several functions that must be run by
a scheduled task (at 6am, 630, 7am, 1130, 230pm). In addition to the
scheduled tasks, users - really just a single user - need to be able to go in
and enter data and run reports.
How can I set up my app so that the macro security message does not come up?
This is imperative for the scheduled tasks to run - if the message comes up,
the task won't run. I have tried signing the app with self cert; this works
UNTIL the other user goes in and runs something. After she closes the app,
neither of us can get in because we get the message regarding the signature
being removed.
From what I can gather, the reason that the signature gets removed is
because something has changed in the app - either action queries, code, or
something else that could become malicious. Well, it's definately NOT code
that is getting changed, but it is likely an action query or 2 that I rewrite
the sql for on the fly (this is necessary).
Any suggestions?
can point me in the right direction.
I have created an application that has several functions that must be run by
a scheduled task (at 6am, 630, 7am, 1130, 230pm). In addition to the
scheduled tasks, users - really just a single user - need to be able to go in
and enter data and run reports.
How can I set up my app so that the macro security message does not come up?
This is imperative for the scheduled tasks to run - if the message comes up,
the task won't run. I have tried signing the app with self cert; this works
UNTIL the other user goes in and runs something. After she closes the app,
neither of us can get in because we get the message regarding the signature
being removed.
From what I can gather, the reason that the signature gets removed is
because something has changed in the app - either action queries, code, or
something else that could become malicious. Well, it's definately NOT code
that is getting changed, but it is likely an action query or 2 that I rewrite
the sql for on the fly (this is necessary).
Any suggestions?