This is a test message from Eudora, and so far I like it
Jim...
This is the code I attempted to send before... testing to see if it gets
SET VAR vy_labelcount INTEGER = 0
SET ERROR VARIABLE errvar
SET VAR vy_errnum INTEGER = NULL
SET VAR vy_log INTEGER = 0
SET VAR vy_errsection TEXT = NULL
SET VAR vy_errcritical INTEGER = 0
--other code
--likely problem section or one I want to log
--Defined Section information goes here
SET VAR vy_errsection = 'So and So View inop'
--CODE GOES HERE
CREATE VIEW junkieview SELECT ALL FROM junkietable
SET VAR vy_errnum = .errvar
IF vy_errnum <> 0 THEN
SET VAR vy_errmsg = 'Error Creating view'
SET VAR vy_errnum = .errvar
SET VAR vy_errcritical = 0 --Non Critical Error
SET VAR vy_labelcount = (.vy_labelcount + 1)
SET VAR vy_errposition TEXT = (CTXT(.vy_labelcount))
--RUN errhndler IN invsum.x2r
GOTO errhdnlr
LABEL &vy_errposition
--GOTO getout1
SHOW VAR
ENDIF
--likely problem section or one I want to log
--Defined Section information goes here
SET VAR vy_errsection = 'Select from table'
--CODE GOES HERE
SELECT ALL FROM junktable
SET VAR vy_errnum = .errvar
IF vy_errnum <> 0 THEN
SET VAR vy_errmsg = 'Error Getting Data'
SET VAR vy_log = 1
SET VAR vy_errcritical = 1 --Critical Error
SET VAR vy_labelcount = (.vy_labelcount + 1)
SET VAR vm_errposition TEXT = (CTXT(.vy_labelcount))
--RUN errhndler IN invsum.x2r
GOTO errhdnlr
LABEL &vy_errposition
--GOTO getout1
SHOW VAR
ENDIF
RETURN
$COMMAND
errhndler
LABEL errhdnlr
OUTPUT SCREEN
SET VAR vy_errmess TEXT = ('ERROR: # ' + (CTXT(.vy_errnum)) + +
' Msg = ' + .vy_errmsg)
PAUSE 1 USING .vy_errmess AT CENTER CENTER
IF vy_log = 1 THEN
OUTPUT mylogfile.log APPEND
WRITE '**************************************'
WRITE .vy_errsection
WRITE .vy_errmess
WRITE '**************************************'
OUTPUT SCREEN
ENDIF
OUTPUT SCREEN
SET VAR vy_errsection TEXT = NULL
SET VAR vy_log = 0
CLEAR VAR vy_errnum, vy_errmess
*(Note .. you could even have a routine here that would determine if an
error was non critical.. Like if vy_errnum in list (1111,2222,3333) then
these are critical errors )
IF vy_errcritical = 1 THEN
--Jump out of routine and inform user of what to do or ???
ELSE
IF vy_errcritical = 0 THEN
GOTO &vy_errposition
ENDIF
ENDIF
SET VAR vy_errcritical INTEGER = 0
RETURN
Not using Outlook, I'm referring to the HTML based system Comcast offers
as a default. I need to setup a client like Outlook or Netscape to do
this, but haven't done this at home yet. I may even get funky and go with
Eudora.. hmmm...
Jim
-------------- Original message --------------
Jim,
If you are using Outlook Express, in your contacts list,
right click on rbg7 > Properties > Name
on the bottom of that page you can click "Send Plain Text"
I'm also using comcast and not having any problems
Bernie Lis
----- Original Message -----
From: <mailto:[EMAIL PROTECTED]>[EMAIL PROTECTED]
To: <mailto:[EMAIL PROTECTED]>RBG7-L Mailing List
Sent: Wednesday, July 07, 2004 7:39 PM
Subject: [RBG7-L] - Re: Tracking Intermediate errors
David.. Well, this is the another time when the code gets chopped
off. I'm going to fuss big time with Comcast over this. They
don't even give any options to send messages in plain text..
They have been bragging about all the new features they added,
and it's about time to put a little dose of reality back into their
vision.
I will resend this from another account.
Jim
-------------- Original message --------------
I've been think a bit here lately of polishing it a bit with a
way to be able to return to the line after the code. Here's
what I have so far.. Rough Draft..
ET VAR vy_labelcount INTEGER = 0
SET ERROR VARIABLE errvar
SET VAR vy_errnum INTEGER = NULL
SET VAR vy_log INTEGER = 0
SET VAR vy_errsection TEXT = NULL
SET VAR vy_errcritical INTEGER = 0
--other code
--likely problem section or one I want to log
--Defined Section information goes here
SET VAR vy_errsection = 'So and So View inop'
--CODE GOES HERE
CREATE VIEW junkieview SELECT ALL FROM
Jim
-------------- Original message --------------
> That is slick code, jim!!
>
> David
>
> David Blocker
> [EMAIL PROTECTED]
> 781-784-1919
> Fax: 781-784-1860
> Cell: 339-206-0261
> ----- Original Message -----
> From: "Jim Limburg"
> To: "RBG7-L Mailing List"
> Sent: Friday, July 02, 2004 3:38 PM
> Subject: [RBG7-L] - Re: Tracking Intermediate errors
>
>
> > What about writing the to a log
> >
> >
> > SET ERROR VARIABLE errvar
> > SET VAR vy_errnum INTEGER = NULL
> > SET VAR vy_log INTEGER = 0
> > SET VAR vy_errsection TEXT = NULL
> >
> > --other code
> >
> > --likely problem section or one I want to log
> > --Defined Section information goes here
> > SET VAR vy_errsection = 'So and So View inop'
> > --CODE GOES HERE
> > IF errvar <> 0 THEN
> > SET VAR vy_errmsg = 'Error Creating view'
> > SET VAR vy_errnum = .errvar
> > RUN errhndler IN invsum.x2r
> > GOTO getout1
> > ENDIF
> >
> >
> > RETURN
> > $COMMAND
> > errhndler
> > OUTPUT SCREEN
> > SET VAR vy_errmess TEXT = ('ERROR: # ' + (CTXT(.vy_errnum)) + +
> > ' Msg = ' + .vy_errmsg)
> > PAUSE 1 USING .vy_errmess AT CENTER CENTER
> > IF vy_log = 1 THEN
> > OUTPUT mylogfile.log APPEND
> > WRITE '**************************************'
> > WRITE .vy_errsection
> > WRITE .vy_errmess
> > WRITE '**************************************'
> > OUTPUT SCREEN
> > ENDIF
> > OUTPUT SCREEN
> > SET VAR vy_errsection TEXT = NULL
> > SET VAR vy_log = 0
> > CLEAR VAR vy_errnum, vy_errmess
> > RETURN
> >
> > Jim
> >
> > Charles Parks wrote:
> >
> > >What are some good strategies for tracking and fixing errors that do
not
> consistently repeat?
> > >
> > >
> > >
> > >
> >
> >
>
