Command-line does work when scheduled

[Gabriel Genellina]

En Sun, 30 Sep 2007 11:42:56 -0300, Jim <jscrerar at compuserve.com> escribi�:

> On Sep 29, 8:45 pm, "Gabriel Genellina" <gagsl-... at yahoo.com.ar>
> wrote:

>> The %* at the end is important: if you created the association by using
>> "Open with...", or selecting Python from the list of installed programs,
>> very likely the command says only "%1" - that is, the script being open,
>> but without any additional arguments.

> I believe I get the correct results as follows:
> ==============================================
> Microsoft Windows XP [Version 5.1.2600]
> (C) Copyright 1985-2001 Microsoft Corp.
>
> J:\Jim Crerar\mypython\misc>assoc .py
> .py=Python.File
>
> J:\Jim Crerar\mypython\misc>ftype Python.File
> Python.File="E:\Python25\python.exe" "%1" %*
>
> J:\Jim Crerar\mypython\misc>
> ===============================================
> What else could be wrong?

No more ideas... I think the scheduler just executes the command line, and  
if it works in a console, should work in the scheduler too... Unless you  
execute the job under another user, who has a different association for  
.py files, that's the only reason I can think of.

-- 
Gabriel Genellina