Shell Functions and DOS executables
- From: "VB_Newby" <VB_Newby@xxxxxxxxxxxxxxxxxxxxxxx>
- Date: 07 Jan 2006 23:40:35 GMT
I'm running a DOS executable from a VB Shell function.
vCnvrtWFMResponse = Shell("cnvrtwfm -l " & InputPathFile,
vbNormalFocus) 'Call the app
The DOS executable converts a file from one format to another.
If it's successful, it looks like this (at the DOS prompt):
cnvrtwfm -l tek00001.wfm
Creating tek00001.dat
It it's unsuccessful, it looks like this (at the DOS prompt):
cnvrtwfm -l tek00001.wfm
Error Converting tek00001.wfm
As you can see, the DOS executable informs the user how things worked
out.
The Shell Function, of course, reports the taskID if it was
successful. However, it's definition of "successful" isn't the same
as my DOS executable. ;-)
Ideally, I'd like to retrieve the command line from the Shell
Function and interrogate the string myself. Another alternative is
to look of the converted file with a DIR Function. This seems kind
of crude.
How can I retrieve the command line output of a Shell'ed DOS
executable?
Any suggestions?
.
- Follow-Ups:
- Re: Shell Functions and DOS executables
- From: Lance Wynn
- Re: Shell Functions and DOS executables
- From: Larry Serflaten
- Re: Shell Functions and DOS executables
- Prev by Date: Re: Performance Tips
- Next by Date: Re: INTODUCTION TO VISUAL BASICS
- Previous by thread: Printing variables to screen, when in debug
- Next by thread: Re: Shell Functions and DOS executables
- Index(es):
Relevant Pages
|