Re: Preserve Clipper error messages on screen
- From: rl <rl@xxxxxxxxxx>
- Date: Fri, 29 Aug 2008 01:46:26 -0700 (PDT)
On Aug 29, 6:42 am, Scott Coffey <n...@xxxxxxxxxxx> wrote:
Clipper application is launched via a desktop shortcut that calls a
batch file which launches the application. If the program bombs out
for some reason, the XP command window closes and the user is returned
to the desktop.
When *I* work with the application I also have a desktop shortcut that
calls a batch file but the last line in my batch file is "CMD" which
leaves the command window open. I then launch the application by
entering the name of the executable. If the program bombs, I am able
to see the error messages issued.
I don't want the user to have to close a command window every time
they exit the application, but I also want them to be able to see any
error messages issued. Is there a way to do this?
Hi Scott
An approach which complements those already suggested would be to
append console output to a text file, eg.
APPNAME.EXE >> applog.txt
While your app's errorhandler might trap the usual runtime errors,
internal errors and GPFs usually bomb right out to DOS. Not that it's
ever happened to me. Ha ha. Their output (I recall from memory) can be
redirected at the command line as in the above example.
Richard
.
- References:
- Preserve Clipper error messages on screen
- From: Scott Coffey
- Preserve Clipper error messages on screen
- Prev by Date: Re: Blinker 1302: DPMI function call nnnnh failed with error code nnh
- Next by Date: Re: Preserve Clipper error messages on screen
- Previous by thread: Re: Preserve Clipper error messages on screen
- Next by thread: Re: Blinker 1302: DPMI function call nnnnh failed with error code nnh
- Index(es):
Relevant Pages
|
Loading