> On 31 Oct 2017, at 9:40 pm, Ben Rubinstein via use-livecode
> wrote:
>
> Is there some way that calling 'shell' enters a context with less permission
> than the app which calls it? And is there something I can do about this?
LiveCode’s shell function on windows is basically telling cmd.exe
nvm my response, my earlier message poofed due to size. *sigh* here goes
again...
one thing you might try is to look at the properties for the scheduled
job. You obviously have it set to "run whether user is logged in or not"
but i'm wondering if "do not store password" box is checked. If it is,
i'm on 10, no clue what earlier versions would look like.
On Tue, Oct 31, 2017 at 10:23 AM, Bob Sneidar via use-livecode <
use-livecode@lists.runrev.com> wrote:
> Windows 10?
>
> Bob S
>
>
>
> ___
> use-livecode mailing list
> use-livecode@lists.runrev.
Windows 10?
Bob S
___
use-livecode mailing list
use-livecode@lists.runrev.com
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-livecode
Hi Bob,
Thanks for taking the trouble to consider this.
The first thing that comes to my mind is, where are you putting the log
file? If you are using a specialfolderpath that only has a context when
logged in, then that might be an issue.
It isn't that, the file is being created, the output
The first thing that comes to my mind is, where are you putting the log file?
If you are using a specialfolderpath that only has a context when logged in,
then that might be an issue. As far as the firewall goes, unless you or your IT
team has intentionally blocked RPC traffic, it should have an
