Dumb Question regarding the Run Command

[Guest themav54]

Hi,

I am trying to open outlook through autoit and it doesn't seem to be working. This is my script file:

Run("outlook.exe", "C:\Program Files\Microsoft Office\Office", @SW_MAXIMIZE)

It says that it cannot find the file specified. Outlook.exe is in that directory. What am I missing? Thanks.

[Guest themav54]

Never mind - I realized that the script file must in the same folder as outlook. Thanks.

Hi,

I am trying to open outlook through autoit and it doesn't seem to be working.  This is my script file:

Run("outlook.exe", "C:\Program Files\Microsoft Office\Office", @SW_MAXIMIZE)

It says that it cannot find the file specified.  Outlook.exe is in that directory.  What am I missing?  Thanks.

<{POST_SNAPBACK}>

[Valik]

[rant]

Jon, CyberSlug, or anybody else for that matter, could you please, please, please explicitly state in the help file that the "filename" parameter must be a full path. For some reason, everybody just assumes the working directory means path to file, even though its an optional parameter. If it was the path to the file, people, why would it be optional?

[/rant]

PS: Jon, you should modify the forum to do something with the [rant] tag

[JSThePatriot]

There are 3 types of programmers/scripters:

Those who think outside the box.

Those who think inside the box.

Those who can't find the box.

-- Me (As far as I know)

@Valik

Just wanted to let you know your sig is coo.

JS

[MHz]

@Lar

Run("outlook.exe", @SW_MAXIMIZE)

;Would not work, outlook has no path that the system knows?

Run("C:\Program Files\Microsoft Office\Office\outlook.exe", @SW_MAXIMIZE)

;Would may work so long as it can see within it's own working directory?

Run("outlook.exe", "C:\Program Files\Microsoft Office\Office", @SW_MAXIMIZE)

;Would not work, outlook has no path that the system knows?

Run("C:\Program Files\Microsoft Office\Office\outlook.exe", C:\Program Files\Microsoft Office\Office", @SW_MAXIMIZE)

;This Does work as is giving the system the path to the executable and the executable knows it's working path?

This is same as making shortcuts, basic commands etc. No bug in Autoit. Nor needing @comspec?

I think that general knowledge has been overlooked here? Do you agree?

Last example works as it can see within it's own working directory.

[CyberSlug]

[rant]

Jon, CyberSlug, or anybody else for that matter, could you please, please, please explicitly state in the help file that the "filename" parameter must be a full path.  For some reason, everybody just assumes the working directory means path to file, even though its an optional parameter.  If it was the path to the file, people, why would it be optional?

[/rant]

Yeah, that should be made clear for the Run and RunWait functions..... Anyone have an idea how to also explain the concept of a working directory in one or two sentences?

[Valik]

Yeah, that should be made clear for the Run and RunWait functions.....  Anyone have an idea how to also explain the concept of a working directory in one or two sentences?

<{POST_SNAPBACK}>

Does it have to be polite...?

[ezzetabi]

When you write a filename without any path, Autoit look for it in @WorkingDir .

That is the folder where the system where pointing at when you called the script.