Can a compiled macro, scheduled as a service......

[Penny123]

interact w/a locked desktop?

I recently upgraded macro scheduler (been lovin it for years btw) to run on new hardware, new operating system (win2k3) and new security model. The last has me vexed, we are now required to lock the desktop when we disconnect from the server (dameware) This has never been a problem before.

The startup macros on my applications still work great, those that run w/command line paramerters to login at least.. but we try to shut the applications down gracefully. Not working of course, now the desktop is locked get focus etc doesn't work, been perusing your topics for a while now and can't quite verify... the question:
If I purchase some Pro licenses, and compile the macro, run it as a service, will it then be able to interact w/the desktop?

If not, what is the best way to close an application within a macro?

[armsys]

Pleae tell us more about:
1. How is the application shutdown in question exactly taking place?
2. Is it a scheduled macro? Is it compiled?
3. The details of the script which causes you trouble.

For a compiled script, you can schedule it with Windows' task schedule.

[Penny123]

They are not compiled, they are scheduled. It is only when the desktop is locked that we have the issue, as well documented in this discussion/your faqs, etc. Leaving the desktop unlocked is not an option, even if we could unlock it via macro/tool/etc, it would not be an acceptable option. I understand that I can compile it and schedule w/windows task scheduler, I just want to know, before I buy the compiler, since I have no other use for it, if I run the macro as a service, can I get it then to do what I need and if not, is there another option?

The macros we run, for example:
Weekly our repository application is reset on the mainframe. The application that adds documents to it will not work while the repository is down. So we schedule a macro to close it, and another log in again when the repository is likely to be up. The launch and log in works fine, command line paramaters are nice, but when we close it we want to be sure that it isn't in the middle of a document, killing the app mid-task may cause partial documents to store, and (hopefully) the whole document to store later as a duplicate. New documents come in 24/7, so we can never be sure that the app won't be processing a document. Ctl-S stops the application between tasks, Ctl-F4 closes it. This it the current macro:


IfWindowOpen>Export*,CloseIt
Goto>END
Label>CloseIt
SetFocus>Export*
WaitWindowClosed>SaveDocument*
Press CTRL
Send Character/Text>S
Release CTRL
Wait>30
SetFocus>Export*
Press ALT
Press F4
Release ALT
WaitWindowClosed>Export*
Label>END


Thanks in advance!

[armsys]

Hi Penny123,

Your script is plain and straightforward. Now I've trouble with the English word "locked", which shows up repetitiously in your post. What do you mean by it? Do you mean the computer ceases to function (forzen/hang)? Do you mean that you wish to deny unauthorized login(s)? Please clarify. Thanks.

[support]

Penny,

Nothing can interract with applications at the gui user level when the o/s is locked/logged out. Nothing. Not macros, compiled macros, or anything else.

When the machine is locked there is no user interface and apps have no windows. So Macro Scheduler macros cannot manipulate them whether compiled or not.

I hope this answers your question.