Kurt,

Thanks for the feedback. Am not currently using Logout. If there are
situations which give me no alternative but to terminate the program - it
seems that Halt() may be appropriate. In any event, I plan on logging error
messages.

Nelson
"Kurt Pawlikowski" <kurtt@pinrod.com> wrote in message
news:A921.1136842305.3072@discuss.softvelocity.com...
> Nelson,
>
> With HALT, your program will shut down immediately. With MESSAGE,
> you can offer, or just notify, recovery. If you wrap your transaction in
> a LOGOUT statement, then a failure would simply ROLLBACK and you can
> notify the user that there was a problem without them having to restart
> the application. In any case, I'd keep a local log with the error
> messages in it. That way you don't have to rely on the customer's
> memory... which is not quite as good as the PC's without power... <g>
>
> Regards,
>
> kurtt
>
> Kurt Pawlikowski
> The Pinrod Corporation
> kurtt@pinrod.com
> (773) 284-9500
> http://pinrod.com
>
> Nelson Kaye wrote:
>
> > Sean,
> >
> > In innumerable places throughout my app, for example, I access record
from a
> > table. If this results in a error in many cases (i.e., LEVEL:NOTIFY), I
> > can't have the user continue. I though this would be a use for halt().
Of
> > course I could use Message(), but then I believe that I would have to
give
> > an Abort option, and have the user contact tech support to resolve the
> > problem before resuming the program.
> >
> > In this case, if my logic is not faulty, what is the difference if I use
> > HALT vs. MESSAGE?
> >
> > Nelson
> >
> > "Sean Cameron" <sean@capesoft.com> wrote in message
> > news:A921.1136801851.2897@discuss.softvelocity.com...
> >
> >>Hi Nelson,
> >>
> >>I would use Neither Halt() nor Stop() in general use. Halt is when
> >
> > something
> >
> >>really genuinely bad has happened and you want you program to Go Away
> >
> > Right
> >
> >>Now, because anything else could result in damage to files etc. This is
> >>normally handled within the ABC classes anyway. Generally I would
display
> >
> > a
> >
> >>message to the user (even if it doesn't give any options, but simply
tells
> >>the user that an error has occurred) and then take any necessary action
as
> >>cleanly as possible
> >>
> >>I can't think of a situation off hand that I would ever leave a stop in
a
> >>release application.
> >>
> >>
> >>--
> >>Regards,
> >>
> >>Sean Cameron
> >>CapeSoft
> >>www.capesoft.com
> >>
> >>Work Smarter, Not Harder!
> >>
> >>"Nelson Kaye" <nkaye1@nyc.rr.com> wrote in message
> >>news:A921.1136793988.2877@discuss.softvelocity.com...
> >>
> >>>In developing a program, I am trying to determine when to use HALT()
vs.
> >>>STOP() vs. MESSAGE().
> >>>
> >>>In reading 'help', I see STOP gives an Abort and Ignore option; HALT
> >>>gives an OK option which aborts the program,[same result, I believe as
> >>>pressing Abort in a Stop()], and MESSAGE lets me choose one or more
> >>>buttons
> >>>which I can react to upon return from the button choice
> >>>
> >>>My general thoughts are as follows:
> >>>1. Use Halt() when I want to force the user out of the program.
> >>>2. Use Stop() to give the user the abort or ignore options without
> >>>further
> >>>program intervention.
> >>>3. Use Message() for all other situations.
> >>>
> >>>Also, I plan on using the 3rd party MesageBox by Capesoft.
> >>>
> >>>Nelson
> >>>
> >>>
> >>>
> >>
> >>
> >>
> >>
> >
> >
> >
>