UPDATE doesn't break debug?

[John Esak]

How utterly funny!  This is yet another example of Hdogkiss's Law of
Simultaneous FilePro Development Timelines...  No one asks about something
and then BOOM! it is everywhere at once.  Honest to God, I asked Ken this
*exact* same question about 10 days ago when I had put an UPDATE in my
@entsel processing and it wasn't working exactly the way I thought it should
have.  It was at this point (again 10 days ago) that ken suggested this
might be a good wish list item!  Too strange.  I wonder if he took the same
double-take I did when I saw this message.

John


> -----Original Message-----
> From: filepro-list-bounces+john=valar.com at lists.celestial.com
> [mailto:filepro-list-bounces+john=valar.com at lists.celestial.com]On
> Behalf Of Kenneth Brody
> Sent: Saturday, March 08, 2008 2:00 PM
> To: Jay R. Ashworth
> Cc: filepro-list at lists.celestial.com
> Subject: Re: UPDATE doesn't break debug?
>
>
> 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.)
>
> --
> KenBrody at BestWeb dot net        spamtrap: <g8ymh8uf001 at sneakemail.com>
> http://www.hvcomputer.com
> http://www.fileProPlus.com
> _______________________________________________
> Filepro-list mailing list
> Filepro-list at lists.celestial.com
> http://mailman.celestial.com/mailman/listinfo/filepro-list