Reminder for @UPDATE

[John Esak]

I'm not sure if this is germane to the topic.  I missed the beginning of the
thread... But, I used @update *without* any screen all the time.  I simply
hit the @update line in the processing... Do all the things I want to do and
then END.  It always seem to work.  In fact in many of my situations I have
done a lookup free to a record to stand on first... (in @menu say) and then
perform the @update stuff *without* any conjugant  screen, and then hit a
"delete;  exit", which writes the current record... And then deletes it. No
problem, no foul. (The EXIT has an implied WRITE built into it, no need to
explicitly use one here.)

I don't think you need to actually get into a field to do valuable
processing or truly "update" the current record.

John
 

> -----Original Message-----
> From: filepro-list-bounces+john=valar.com at lists.celestial.com 
> [mailto:filepro-list-bounces+john=valar.com at lists.celestial.co
m] On Behalf Of Kenneth Brody
> Sent: Thursday, November 12, 2009 1:39 PM
> To: Boaz Bezborodko
> Cc: filepro-list at lists.celestial.com
> Subject: Re: Reminder for @UPDATE
> 
> Boaz Bezborodko wrote:
> > I seem to remember that when using @UPDATE I have to enter 
> a SCREEN ,x 
> > command to get it to move to the first field on the cursor 
> path.  Is 
> > this correct?
> [...]
> 
> When your @UPDATE handler ends, update mode ends.  If you 
> never executed a 
> SCREEN command (or something similar, such as POPUP UPDATE), 
> then the user 
> will never be updating a screen.
> 
> -- 
> Kenneth Brody
> _______________________________________________
> Filepro-list mailing list
> Filepro-list at lists.celestial.com
> http://mailman.celestial.com/mailman/listinfo/filepro-list
>