C
Clif McIrvin
I 'm familiar with the process of embedding a clickable link to a file
located on a share accessible to the recipient, and do so regularly by
using a UNC formatted path:
\\ServerName\Path\to the \location\of the\file
(Interesting ... the "<" ">" I wrapped the above line in dissappeared as
soon as I entered the close bracket. In Outlook [plain text] I'm not
used to that happening.)
My question: is it possible to do the same thing to launch a .exe (or
..cmd) with command line arguments?
Something like:
\\UNC Path\Executable /argument1 /argument2=some text string /arg3 etc
that line with extra quotes and spaces:
"<" \ \ UNC Path\Executable /argument1 /argument2=some text string /arg3
etc ">"
I'm using WinXP Pro SP3 with Office (Outlook) 2003 SP3 and IE8 Update
Version 0, however, I'd like confidence that the embedded link will work
regardless of the Windows / Office version being used.
[I am presently living with the Security Risk warnings that Outlook
loves to throw and just asking my users to go ahead and run the link.]
located on a share accessible to the recipient, and do so regularly by
using a UNC formatted path:
\\ServerName\Path\to the \location\of the\file
(Interesting ... the "<" ">" I wrapped the above line in dissappeared as
soon as I entered the close bracket. In Outlook [plain text] I'm not
used to that happening.)
My question: is it possible to do the same thing to launch a .exe (or
..cmd) with command line arguments?
Something like:
\\UNC Path\Executable /argument1 /argument2=some text string /arg3 etc
that line with extra quotes and spaces:
"<" \ \ UNC Path\Executable /argument1 /argument2=some text string /arg3
etc ">"
I'm using WinXP Pro SP3 with Office (Outlook) 2003 SP3 and IE8 Update
Version 0, however, I'd like confidence that the embedded link will work
regardless of the Windows / Office version being used.
[I am presently living with the Security Risk warnings that Outlook
loves to throw and just asking my users to go ahead and run the link.]