Vista - Passing "| find" in command executed with EXEC method does not work

If I try to pass "| find" command with psinfo, executed with the EXEC
method I get a syntax error from psinfo. If I take the EXACT command
and run it at the command prompt it works fine. Any thoughts on why
this does not work?

---------------begin code------------------
compName = "SERVER1"
var1 = "c:\catapult\pstools\psinfo applications -s \\" & compName & "
| find /V " & chr(34) & "Security Update" & chr(34) & " | find /V " &
chr(34) & "Update for Windows" & chr(34) & " | find /V " & chr(34) &
"Hotfix" & chr(34)
msgbox var1
var2 = ExecCmd(var1)
wscript.echo var2

Function ExecCmd(Command)
Dim oExec,WshShell, Line

Set WshShell = WScript.CreateObject("WScript.Shell")
Set oExec = WshShell.Exec(Command)
Line = ""
Do while oExec.Status <> 1
If not oExec.StdOut.AtEndOfStream Then
line = line & oExec.StdOut.ReadAll
End If
If not oExec.StdErr.AtEndOfStream Then
line = line & oExec.StdErr.ReadAll
End If
Loop
ExecCmd = Line
End Function
-------------end code-----------------

Thanks in advance,
Steve

On Aug 4, 4:18*pm, Steve <collamp...@xxxxxx> wrote:Piping is supported by the command processor, so it needs to be
invoked directly ...

Set oExec = WshShell.Exec("%comsoec /c " &Command)

Tom Lavedas
***********

On Aug 4, 4:37*pm, Tom Lavedas <tglba...@xxxxxx> wrote:Thanks for the reply Tom. Forgive if this is a n00b question, but
what does "%comsoec /c" refer to in your post?

I appreciate your help.

Steve

"Steve" <collampton@xxxxxx> wrote in message
news:9c0ac0ef-217b-4831-b1da-e6f1ecf9bfde@xxxxxxFurther to Tom's reply: Running a VB Script program and invoking find.exe
three times is not "nice". VB Script has its own "find" function (instr),
and using it would not only avoid your three pipes but it would also speed
up your script enormously. This may not matter much in this particular case
but it does when you invoke find.exe many times.

On Aug 4, 5:43*pm, Steve <collamp...@xxxxxx> wrote:Well, first I need to apologize. I was in a hurry and introduced two
errors into what I typed. It should not be "%comsoec /c ", but rather
"%comspec% /c ". Sorry for any confusion I caused by my haste.

That is the environment variable generated by the system to point to
the correct location for the command processor - usually cmd.exe,
these days. If you drop to a command prompt and type SET COMS followed
by the Enter key, you will see what is stored in the variable. It is
almost always C:\Windows\system32\cmd.exe, but it doesn't have to be.
For example, I have an upgraded Win2K machine at home that returns C:
\WinNT\system32\cmd.exe. Still, if the PATH statement points to the
%SystemRoot%\system32 location, a simple call to CMD.EXE will
suffice. I make it a habit to use the COMSPEC variable just to be
that much more certain I get the result I expect.

Tom Lavedas
***********

On Aug 4, 4:49*pm, "Pegasus [MVP]" <n...@xxxxxx> wrote:lol...sometimes it's not easy being a hack.

OK, I will try to rework my approach using a "nicer" method. :-)

Thanks,
Steve

On Aug 4, 4:59*pm, Tom Lavedas <tglba...@xxxxxx> wrote:No problem at all, and thanks so much for the help. This is really
good info!

I've gotten two good pointers so hopefully I can make progress now.

Thanks again,
Steve

On Aug 4, 5:02*pm, Steve <collamp...@xxxxxx> wrote:Thanks again Tom and Pegasus. I used both of your suggestions
("%comspec% /c " in my EXEC statement and nested IF logic with InStr
statements instead of piping to FIND.EXE) and have a faster running,
functional script.