UPDATE doesn't break debug?

[Jay R. Ashworth]

On Sat, Mar 08, 2008 at 02:00:11PM -0500, Kenneth Brody wrote:
> Quoting Jay R. Ashworth (Sat, 8 Mar 2008 10:47:54 -0500):
> [... Using UPDATE in @ENTSEL ...]
> >having difficulty further down the code, and when I run the table in
> >-DB, *UPDATE does not take me to entry mode on the screen*.
> >
> >*I* call that a bug, can anyone disagree?
> [...]
> 
> As the manual states, UPDATE is for automatic processing, and means "when
> automatic processing ends, take me into update mode".  It does not mean
> "immediately enter update mode".  (Though I could see a withlist item to
> extend UPDATE to work the same way from @ENTSEL as well as automatic.)

Well... will SCREEN take @sn as a parameter?  (Or by lack of any
parameter, I suppose.)  That would be suitableas an alternative.

While we're talking about automatic, BTW, was there ever a formal
solution implemented to "automatic processing runs multiple times;
which time is this?"

Cheers,
-- jra
-- 
Jay R. Ashworth                   Baylink                      jra at baylink.com
Designer                     The Things I Think                       RFC 2100
Ashworth & Associates     http://baylink.pitas.com                     '87 e24
St Petersburg FL USA      http://photo.imageinc.us             +1 727 647 1274

	     Those who cast the vote decide nothing.
	     Those who count the vote decide everything.
	       -- (Joseph Stalin)