Conference abbott::visual_basic

2508.0. "errors from SHELLed app" by NUBOAT::HEBERT (Captain Bligh) Mon Mar 03 1997 16:21

I have a VB4 app that runs on an Alpha NT 4.0 with FX!32 running. This
app constructs a command line to run a command-line-only app that is
Alpha-native. This much is working fine. My problem lies in error
collection.

If I pop a command line window and type in a full command line (with
options etc), the target app runs fine; any errors are sent to that
window. If I add 2> ERROR.TXT to the command line, when the target app
runs all errors are indeed routed to the ERROR.TXT file, which it
happily creates.

However, when I use SHELL to fire that exact same command line off from
within my VB4 app, the errors do *not* get rerouted to the file. 

Where are they going? (No file gets created anywhere; I used DIR/S to
look for them.)

Is there a way to force that SHELLed process to reroute its STDERROR to a
text file? SHELL itself {RetVal (SHELL "foo.exe",1)} returns the task ID
number in RetVal that simply says foo.exe executed; it does not relate to
any errors generated within foo.exe. 

Thanks,

Art